Repository navigation
fix(ci): close the release issue once the release is cut - #61
Merged
Merged
Conversation
release-please files "Release X is ready to open" when the org blocks it from creating the PR, and nothing closed it afterwards — one dead issue per release, each pointing at work already done. Three had accumulated across both repos. The release existing is the definitive done signal, so it closes there.
Merged
srbiv
added a commit
that referenced
this pull request
Aug 11, 2026
Automated Release PR --- ## [2.8.4](v2.8.3...v2.8.4) (2026-08-11) ### Bug Fixes * **ci:** close the release issue once the release is cut ([#61](#61)) ([a8fcac5](a8fcac5)) --- Opened by `scripts/open-sdk-release.mjs` in tabstack-api-docs, because GitHub Actions may not create pull requests in this org. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
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.
release-please files a "Release X is ready to open" issue when the org blocks it from creating the PR. Nothing ever closed it, so they accumulate — one dead issue per release, each telling you to do work already done. Three had built up across the two SDK repos before I noticed.
Closes the matching issue right after
github-releasesucceeds, gated on the samereleasedoutput that gates publishing. The release existing is the definitive done signal.Companion to the same fix on the codegen side in tabstack-api-docs#27.