ci(release): add next release summary to workflow page - #4919
Conversation
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6182b38e2c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| echo "- **Tag:** \`next\`" | ||
| echo "- **Branch:** \`${{ github.event.inputs.branch }}\`" | ||
| echo "- **Version:** \`$VERSION\`" | ||
| echo "- **Commit:** \`${{ github.sha }}\`" |
There was a problem hiding this comment.
When a manual release is dispatched from one ref but the branch input points checkout at another ref, this summary records the workflow ref's SHA rather than the commit that was actually built and published. GitHub documents workflow_dispatch GITHUB_SHA as the last commit on the GITHUB_REF branch/tag that received the dispatch, while this workflow publishes ${{ github.event.inputs.branch }} via actions/checkout; use git rev-parse HEAD after checkout so the run summary remains a reliable release audit trail.
Useful? React with 👍 / 👎.
@module-federation/devtools
@module-federation/cli
create-module-federation
@module-federation/dts-plugin
@module-federation/enhanced
@module-federation/error-codes
@module-federation/esbuild
@module-federation/managers
@module-federation/manifest
@module-federation/metro
@module-federation/metro-plugin-rnc-cli
@module-federation/metro-plugin-rnef
@module-federation/metro-plugin-rock
@module-federation/modern-js
@module-federation/modern-js-v3
@module-federation/native-federation-tests
@module-federation/native-federation-typescript
@module-federation/nextjs-mf
@module-federation/node
@module-federation/observability-plugin
@module-federation/playground
@module-federation/retry-plugin
@module-federation/rsbuild-plugin
@module-federation/rspack
@module-federation/rspress-plugin
@module-federation/runtime
@module-federation/runtime-core
@module-federation/runtime-tools
@module-federation/sdk
@module-federation/storybook-addon
@module-federation/third-party-dts-extractor
@module-federation/treeshake-frontend
@module-federation/treeshake-server
@module-federation/typescript
@module-federation/utilities
@module-federation/webpack-bundler-runtime
@module-federation/bridge-react
@module-federation/bridge-react-webpack-plugin
@module-federation/bridge-shared
@module-federation/bridge-vue3
@module-federation/inject-external-runtime-core-plugin
commit: |
Bundle Size Report6 package(s) changed, 36 unchanged. Bundle targets
Consumer scenarios
Total dist (raw): 35.79 MB (no change) Bundle sizes are generated with rslib (Rspack). Package-root metrics preserve the historical report. Tracked subpath exports such as |
1 participant
What changed
Adds an inline
Release summarystep at the end of the release workflow that writes to the GitHub Actions run summary page ($GITHUB_STEP_SUMMARY). The step reports the release tag, branch, published version, and commit hash.Why
After a release runs there was no at-a-glance record of what was released on the workflow run page. Surfacing the version and commit directly in the run summary makes it easy to confirm what went out without digging through job logs.
Details
nextchannel only (if: success() && github.event.inputs.version == 'next').packages/runtime/package.json(@module-federation/runtime), which is part of thefixedversion group in.changeset/config.json. All packages in that group share the same snapshot version onnext, so this single value is the canonical release version.${{ github.sha }}.User / runtime impact
CI-only change. No package behavior changes and nothing is published or altered by this step; it only appends markdown to the workflow summary.
Validation
packages/runtimeresolves to@module-federation/runtimeand is a member of the changesetfixedgroup.lint-fix(Prettier) andcommitlinthooks.Skipped checks
No build/test/e2e checks were run: this is a CI-workflow-only change with no package code impact, so per the repo's task-to-checks table those gates are not applicable.