Skip to content

fix: normalize release smoke inputs #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
envoy1084 merged 2 commits into from
Oct 27, 2026
Merged

fix: normalize release smoke inputs #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
476db7c
docs: explain PR metadata checks
envoy1084 Oct 27, 2026
560fda0
fix: normalize release smoke dispatch inputs
envoy1084 Oct 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .github/workflows/release-smoke.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ jobs:
smoke:
uses: effect-kit/.github/.github/workflows/release-smoke.yml@v1
with:
release-run-id: ${{ inputs.release-run-id }}
pack-artifact-id: ${{ inputs.pack-artifact-id }}
# Manual dispatch supplies IDs as strings; the reusable workflow expects numbers.
release-run-id: ${{ fromJSON(inputs.release-run-id) }}
pack-artifact-id: ${{ fromJSON(inputs.pack-artifact-id) }}
bun: true
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,10 @@ CI, PR-title checks, Changeset summaries, releases, and registry smoke checks re
[EffectKit's shared workflows](https://github.com/effect-kit/.github). Runtime versions
and package-specific checks stay in this repository's scripts.

PR titles follow Conventional Commits, for example `fix: preserve binary values`.
Changeset release impact appears in the Actions job summary; documentation-only PRs
do not need a Changeset.

Changesets manages package versions and changelogs. Add a Changeset with public API
changes, commit it with the code, and dispatch **Release** on `main` with `dry-run` disabled
to create or update the version PR. After reviewing and merging that PR, dispatch **Release**
Expand Down
Loading