Skip to content

feat: add release manifest artifact#178

Closed
Samielakkad wants to merge 1 commit into
canonical:mainfrom
Samielakkad:codex/release-manifest-artifact
Closed

feat: add release manifest artifact#178
Samielakkad wants to merge 1 commit into
canonical:mainfrom
Samielakkad:codex/release-manifest-artifact

Conversation

@Samielakkad

@Samielakkad Samielakkad commented Jul 13, 2026

Copy link
Copy Markdown

Summary

  • capture pip freeze output in manifest.txt for each upload-charm publication
  • upload the manifest with collision-safe artifact names
  • migrate manifest and charmcraft-log uploads to the current immutable artifact backend
  • keep manifest and log collection independent so one failure cannot suppress the other
  • cover generation, upload arguments, unique naming, failure paths, and action integration with focused tests
  • rebuild the committed JavaScript action bundles

Closes #20

Validation

  • npm test (62 tests passed)
  • npm run lint
  • npx tsc --noEmit
  • npm run build
  • focused Prettier check on changed TypeScript files
  • Node 24 compatibility check across package engine constraints

@Samielakkad Samielakkad marked this pull request as ready for review July 13, 2026 16:47
@Samielakkad Samielakkad changed the title [codex] add release manifest artifact feat: add release manifest artifact Jul 13, 2026
@Samielakkad Samielakkad force-pushed the codex/release-manifest-artifact branch from 02fb865 to 129f7a0 Compare July 13, 2026 18:17
@Samielakkad Samielakkad force-pushed the codex/release-manifest-artifact branch from 129f7a0 to e8c651a Compare July 13, 2026 18:28
@Samielakkad Samielakkad deleted the codex/release-manifest-artifact branch July 14, 2026 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reroute pip freeze to a manifest.txt file and attach that to the release as an artifact

1 participant