-
-
Notifications
You must be signed in to change notification settings - Fork 490
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
Release gems in batch #1449
Comments
Cool stuff, also we should have one changelog in release with different sections like we have in JS monorepo https://github.com/getsentry/sentry-javascript/releases/tag/6.4.1 So our users always can look at the release and changelog to understand what changed. (The only downside is potential no-op releases for packages which is something we def. can live with) |
@HazAT yeah that's part of the main drive behind this decision 😄 |
This is now completed with the help from @BYK 😉 |
Current Workflow & Problems
Currently, all gems are all prepared and released individually. It's great for releasing patch version individually, but it also makes releasing minor versions complicated. Here's the general workflow:
sentry-ruby
's releasesentry-ruby
to be publishedsentry-rails
)sentry-ruby-core
dependency version.sentry-ruby
is merged to master.Also, we can't have a shared changelog under the current releasing structure due to potential version collision.
New Workflow
Definition of the new workflow:
sentry-raven
) will always be released under the same version.sentry-sidekiq
to4.4.4
, othersentry-*
gems will also be bumped and released with version4.4.4
, regardless they have change or not.sentry-raven
will still be released solely.And the new release process will be:
The text was updated successfully, but these errors were encountered: