Repository navigation
chore(release): release CLI 0.20.0 with the remote key check - #640
Conversation
envilder validate checking that every declared secret exists was merged in #637 after v0.19.0 was tagged, but its changelog entries were added to the already released 0.19.0 sections, and the version was not bumped. Move them to a new 0.20.0 section and bump the version so the release workflow publishes the feature.
github-actions
Bot
added
chore
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Align version and release records package.json, docs/changelogs/cli.md, docs/changelogs/gha.md, ROADMAP.md |
The package version and latest release headings change to 0.20.0. The CLI changelog adds the 0.20.0 entry, and the GitHub Actions changelog adds a 0.19.0 entry. The roadmap updates the remote key existence check availability to CLI v0.20.0. |
Estimated code review effort: 2 (Simple) | ~5 minutes
Possibly related PRs
- macalbert/envilder#637: Adds the remote secret-existence check documented in this release.
- macalbert/envilder#630: Adds the offline validation check retained in the roadmap entry.
- macalbert/envilder#639: Uses changelog sections and release notes in the publishing workflow.
Merge Risk: 
962f4
-
The release metadata is consistent and presents no identified merge-blocking risk.
Pre-merge checks: 
-
Check name Status Explanation Title check The title follows the Conventional Commits format type(scope): subjectwith the allowed typechoreand scoperelease. The subject is lowercase and the title is 60 characters, under the 100-chara…Description check The description follows the repository template. It includes a clear summary of the change and the reason for it. It lists the changed files and the testing done, and it links related issue #637. The …Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Architecture Boundaries The pull request changes only ROADMAP.md, docs/changelogs/cli.md, docs/changelogs/gha.md, and package.json. No changed file is under src/envilder/core/domain/ or src/envilder/core/application/, so the… Tests Accompany Code Changes PASS. The pull request changes only ROADMAP.md, changelog Markdown files, and package.json. It changes no files under src/envilder/, src/sdks/, tests/, or e2e/. Therefore, it introduces no in-scope be… Release Coherence The PR changes the root package.json version from 0.19.0 to 0.20.0. It also adds the CLI 0.20.0 changelog entry under docs/changelogs/cli.md, including the envilder validate provider check. The releas… Full details: Title check
-
Explanation
The title follows the Conventional Commits format
type(scope): subjectwith the allowed typechoreand scoperelease. The subject is lowercase and the title is 60 characters, under the 100-character limit. It matches the main change, which bumps the CLI version to 0.20.0 and moves the secret-existence changelog entries to a new 0.20.0 section.
Full details: Description check
-
Explanation
The description follows the repository template. It includes a clear summary of the change and the reason for it. It lists the changed files and the testing done, and it links related issue
#637. The 'Related issues' section is present, but the description does not state a 'Type of change' checkbox and the Checklist items are unchecked, except for the testing items the author marked. The 'Notes for reviewer' section is missing. These gaps are non-critical.
Full details: Architecture Boundaries
-
Explanation
The pull request changes only ROADMAP.md, docs/changelogs/cli.md, docs/changelogs/gha.md, and package.json. No changed file is under src/envilder/core/domain/ or src/envilder/core/application/, so the specified import-boundary failures do not apply.
Full details: Tests Accompany Code Changes
-
Explanation
PASS. The pull request changes only ROADMAP.md, changelog Markdown files, and package.json. It changes no files under src/envilder/, src/sdks/, tests/, or e2e/. Therefore, it introduces no in-scope behavior change without accompanying tests.
Full details: Release Coherence
-
Explanation
The PR changes the root package.json version from 0.19.0 to 0.20.0. It also adds the CLI 0.20.0 changelog entry under docs/changelogs/cli.md, including the envilder validate provider check. The release coherence condition is satisfied.
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
github-actions
Bot
added
the
chore
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Summary
envilder validatechecking that every declared secret exists (#637) was merged afterv0.19.0was tagged, but its changelog entries were added to the already released 0.19.0 sections and the version was never bumped, so the feature is not published. This moves the entries to a new 0.20.0 section and bumps the CLI version, so merging this publishes CLI 0.20.0 throughpublish-npm.yml.Changes
[0.19.0]to a new[0.20.0] - 2026-11-01section indocs/changelogs/cli.md, and the "Secret existence check in the provider adapters" entry indocs/changelogs/gha.md. The remaining 0.19.0 entries match what the tag shipped.package.jsonfrom 0.19.0 to 0.20.0. The version-consistency test requires the latest changelog version to match it, and the publish workflow releases when it changes.The GitHub Action bundle is unchanged by the bump (
pnpm build:ghaproduces no diff), and its release is still published separately withpublish-action.yml.Testing
vitest run tests/website/changelogs: 30 passed (includes the version-consistency check)markdownlinton the changed Markdown passespnpm build:ghaproduces no diff ingithub-action/dist/index.jsoraction.ymlpnpm test(runs in CI)Related
#637
Summary by CodeRabbit