Prepare next release: v3.4.0 #86
Closed
Conversation
This file contains 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
|
@tdreyno Happy with doing the release by myself if you can give me access to push the gem (My RubyGems account: https://rubygems.org/profiles/markets). |
|
@markets rubygems invite sent |
|
Got it! Accepted ✅ Thanks @tdreyno Maybe it makes sense to have access to the repo too 🤔? So I'd be able to merge, push and close issues (and release from canonical master branch, instead of my fork). Of course, I'd ask for your help/feedback before any relevant change here. |
|
@markets done. made you a maintainer in GitHub for this repo |
|
Thanks @tdreyno! Will release this later 🚀 |
|
Deleted my fork and recreated from this repo in 👉🏼 #87 |
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.
@tdreyno opening this PR to propose to cut a new release (
v3.4.0) to RubyGems.Current diff: d1b3edd...master
Took the opportunity to fill the missing Changelog entry for current v3.3.0 and refactor a bit the file.