-
Notifications
You must be signed in to change notification settings - Fork 15
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
chore: GCDS Components Release v0.21.0 #487
Conversation
What we still need to do in each Release PR:
Reminder |
b508a7a
to
35d4f49
Compare
e2ae4cb
to
ab2657f
Compare
ab2657f
to
ba9802f
Compare
2ce5ef7
to
00e586e
Compare
00e586e
to
5651759
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.
Let's ship this - wohoo
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.
Since we're maintaining the 3 changelogs as well, and they will show up on the releases page: https://github.com/cds-snc/gcds-components/releases
Can we update them to reflect the breaking changes too? I think it's okay to just flag the breaking changes and then link them to the root changelog for the details of how to deal with the updates.
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.
🚐 LGTM!
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.
Ready to go!!
🤖 I have created a release beep boop
gcds-components: 0.21.0
0.21.0 (2024-05-08)
New Features
Bug Fixes
gcds-components-angular: 0.21.0
0.21.0 (2024-05-08)
New Features
Dependencies
gcds-components-react: 0.21.0
0.21.0 (2024-05-08)
New Features
Dependencies
This PR was generated with Release Please. See documentation.