New release #79
Merged
New release #79
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
9 tasks
kiskoza
force-pushed
the
release-0.4.6
branch
from
d6aea04
to
1f88052
Compare
kiskoza
force-pushed
the
release-0.4.6
branch
2 times, most recently
from
ec92f81
to
891b67d
Compare
kiskoza
force-pushed
the
release-0.4.6
branch
from
891b67d
to
6f4bdb5
Compare
|
@bf4 @jnunemaker I'm ready with all the pre-release tasks I wanted to do before we can release the new I'm happy to merge in this PR and tag the new release commit in the repo any time from now. Let me know if you would like to add anything else. Also, could you help me with releasing it to RubyGems? |
bf4
reviewed
Jan 29, 2024
bf4
reviewed
Jan 29, 2024
| @@ -1,25 +1,26 @@ | |||
| # crack | |||
|
|
|||
| [](https://travis-ci.org/jnunemaker/crack) | |||
| [](https://github.com/jnunemaker/crack/actions/workflows/test.yml) | |||
|
Looks good |
|
Released 0.4.6 |
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.
We already have a few fixes merged in, we should do a release soon to make sure that this gem remains usable.
ToDo:
My Questions:
Should we add a minimum Ruby version?
I wasn't able to set up the environment for Ruby <2.0, and there are already EOL for ages.
Should we release it as 1.0.0 as well?
The gem seems to be really stable, but most of the gems / projects are referencing it as
~> 0.4.x, so we definitely need a0.4.6first.