-
Notifications
You must be signed in to change notification settings - Fork 1
chore(main): release init 1.2.0 #79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
chore(main): release init 1.2.0 #79
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the
Comment |
cbf183d to
e9517ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3 files reviewed, 1 comment
| * prevent desktop asset and jsx runtime errors ([cba616b](https://github.com/metaideas/init/commit/cba616b547b0df13b6cc5f9529c9964c176b885b)) | ||
| * update url env var validation ([4c9014f](https://github.com/metaideas/init/commit/4c9014f98db496b16cba47dccd8d034b5a214160)) | ||
| * update url env var validation ([8aa4a75](https://github.com/metaideas/init/commit/8aa4a752a41d5c9af783e4c1c15ab9bcb99d3662)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] The 1.1.1 changelog lists the same bullet title twice (update url env var validation) with different commit SHAs. If this is the same fix cherry-picked/reverted/reapplied, it may be worth consolidating into a single entry to avoid confusing release notes.
Prompt To Fix With AI
This is a comment left during a code review.
Path: CHANGELOG.md
Line: 8:10
Comment:
[P2] The 1.1.1 changelog lists the same bullet title twice (`update url env var validation`) with different commit SHAs. If this is the same fix cherry-picked/reverted/reapplied, it may be worth consolidating into a single entry to avoid confusing release notes.
How can I resolve this? If you propose a fix, please make it concise.e9517ef to
6e75581
Compare
6e75581 to
e9af40c
Compare
🤖 I have created a release beep boop
1.2.0 (2026-02-01)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.
Greptile Overview
Greptile Summary
Automated release PR that bumps version from 1.1.0 to 1.2.0. This release includes one new feature for trusted origins configuration in auth and three bug fixes for desktop assets, JSX runtime errors, and URL environment variable validation.
Confidence Score: 5/5
Important Files Changed
Sequence Diagram
sequenceDiagram participant ReleaseBot as Release Please Bot participant Git as Git Repository participant Files as Version Files ReleaseBot->>Git: Detect commits since v1.1.0 ReleaseBot->>ReleaseBot: Generate changelog entries ReleaseBot->>Files: Update .template-version.json (1.1.0 → 1.2.0) ReleaseBot->>Files: Update package.json (1.1.0 → 1.2.0) ReleaseBot->>Files: Prepend CHANGELOG.md with v1.2.0 entries ReleaseBot->>Git: Create PR #79