chore(release): promote v0.6.2 to main#400
Merged
Merged
Conversation
… runner The release.yml workflow checks out the dispatched ref (the v<version> tag), so the runner's local branches do not include refs/heads/main even with `fetch-depth: 0`. The earlier readiness check only consulted `refs/heads/main` / bare `main`, so every dispatch failed Layer 1 with: RELEASE_READINESS_TAG_NOT_AT_MAIN: could not resolve `refs/heads/main` Fall back to `refs/remotes/origin/main` (which the workflow checkout populates) before bare `main`. Surfaced by the v0.6.1 dry-run dispatch. Add regression test covering the workflow-runner path: tag readiness must pass when only `refs/remotes/origin/main` resolves.
fix(readiness): resolve main via refs/remotes/origin/main on workflow runner
v0.6.2 is a patch release unblocking the v0.6.x release dispatch path: - Layer 1 readiness resolves `refs/remotes/origin/main` (#397). - scripts/cli.ts VERSION derived from package.json (#395). - scripts/check-product-page.ts YAML-scope fixes (#395). - scripts/init-project.ts --target relative path resolution (#396). CHANGELOG, README badge + status, docs/specorator.md header, plugin manifest regenerated from the bumped package.json.
chore(release): bump 0.6.1 -> 0.6.2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release branch for
v0.6.2per ADR-0020. Promotes the v0.6.2 bundle fromdevelopand resolves divergence withmain.Supersedes #399 (which was a direct
develop→mainPR; closed in favor of the canonical release-branch flow).Commits in this promotion
chore(release): bump 0.6.1 -> 0.6.2— patch release bundle.fix(readiness): resolve main via refs/remotes/origin/main on workflow runner— unblocks the v0.6.1 dispatch failure (RELEASE_READINESS_TAG_NOT_AT_MAIN).main(#396init-project caller-cwd fix etc.) into the release branch.Post-merge release path
Per
docs/release-operator-guide.md:main;git tag v0.6.2 <SHA>andgit push origin v0.6.2.RELEASE_VERSION=0.6.2 RELEASE_CI_STATUS=green RELEASE_VALIDATION_STATUS=pass npm run check:release-readiness -- --json→{"diagnostics": []}.gh api repos/Luis85/agentic-workflow/immutable-releases→ 404).release.ymlwithversion=0.6.2,dry_run=true.dry_run=false,confirm=0.6.2,publish_package=true.Test plan
v0.6.2tag cut on themainmerge commit.@luis85/agentic-workflow@0.6.2.release/v0.6.2branch deleted post-publish perdocs/branching.md.🤖 Generated with Claude Code