chore: add changesets for unreleased 0.7.0 → 0.8.0 work#81
Merged
Conversation
The serve-hardening and CLI work since v0.7.0 (PRs #76, #77, #78, #79) merged without changesets, so the Release workflow had nothing to consume and the package is still published at 0.7.0. Add the missing changesets so the next release captures this work. - serve-api-webhook-hardening (patch): #76 - envelope webhook-route errors plus tunnel / Postgres-receipt / broadcast / base-path fixes (10 defects). - webhook-secret-fail-open (patch): #77 - single WEBHOOK_SECRET_ENV source of truth for the tunnel gate + stricter KANBAN_SYNC_INTERVAL_MS parsing. - honor-default-task-column (patch): #78 - SQLite createTask honors the configured default task column, with first-column fallback parity with Postgres. - strict-jira-board-id (minor): #79 - a malformed JIRA_BOARD_ID now throws INVALID_CONFIG instead of being silently misparsed (behavior change). Net bump: minor -> 0.8.0. #80 (pure internal refactor) and the README link fix are intentionally omitted as they have no user-facing change. Claude-Session: https://claude.ai/code/session_01X9j5Rs6kXK8BuHguhy3x33
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
1 participant
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.
Why
The serve-hardening and CLI work merged since v0.7.0 landed without changesets, so the Release workflow has had nothing to consume — the package is still published at
0.7.0despite five PRs onmain. This PR adds the missing changesets so the Changesets action can open the "Version Packages" PR and cut the next release.Changesets added
serve-api-webhook-hardeningwebhook-secret-fail-openWEBHOOK_SECRET_ENVsource of truth closes the tunnel fail-open; stricterKANBAN_SYNC_INTERVAL_MSparsing.honor-default-task-columncreateTaskhonors the configured default task column, with first-column fallback parity with Postgres.strict-jira-board-idJIRA_BOARD_IDnow throwsINVALID_CONFIGinstead of silent misparse (behavior change).Net version bump:
0.7.0→0.8.0(bunx changeset statusconfirms minor).Intentionally omitted
parsePositiveIntrefactor) — pure internal cleanup, no user-facing change.8177296) — docs only.Verification
bunx changeset status→ bumps@andypai/agent-kanbanto0.8.0, consuming all 4 changesets.On merge, the Release workflow opens the Version Packages PR (bumps
package.json+ writesCHANGELOG.md); merging that publishes0.8.0to npm and tags it.https://claude.ai/code/session_01X9j5Rs6kXK8BuHguhy3x33