feat: automate releases with Release Please - #92
Merged
Conversation
longlho
marked this pull request as ready for review
August 6, 2026 13:07
longlho
pushed a commit
that referenced
this pull request
Aug 6, 2026
🤖 I have created a release *beep* *boop* --- ## 0.10.0 (2026-08-06) ## What's Changed * feat: add FormatJS CLI versions through 1.2.0 by @longlho in #91 * feat: automate releases with Release Please by @longlho in #92 **Full Changelog**: v0.9.1...v0.10.0 --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
MODULE.bazelversion blank by tracking Release Please state inversion.txtAdapted from
perplexityai/watchman. This repo uses Release Please'ssimplestrategy because its BCR source module must keep an empty version.
Before merge
Add
GH_RELEASE_TOKENas a Classic PAT withrepoandworkflowscopes.Release Please needs that token so its tag event starts
release.yaml.Test
bazel test //...oxfmt --checkon changed YAML, JSON, and Markdown