Update Ascii85 1.1.0 → 1.1.1 (patch) #3385
Merged
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
Commits
See the full diff on Github. The new version differs by 21 commits:
History.txt: Set release date
Update History.txt
README: Link to archive.org version of the PLRM
bin/ascii85: Fix version display
bin/ascii85: Bail with exit status 1 when command-line parsing fails
Gemspec: Don't build GitHub workflow into the Gem release
README: Make Wikipedia link use HTTPS
README: Fix link to Adobe's PostScript spec
History.txt: Add thanks to the contributors
README: Remove `Contributors` section
Bump version and update History.txt
♻️ File.exists? -> File.exist?
ci: Add Ruby 3.3 to build matrix
Revert "ci: remove Ruby 3.2 from build matrix (not supported yet)"
ci: remove Ruby 3.2 from build matrix (not supported yet)
ci: update workflow according to ruby/setup-ruby README
Add Ruby 3.2 to CI
Add Ruby 3.1 to CI
ci: add `head`, `jruby` and `truffleruby` to the build matrix
ci: setup GitHub Actions to automatically run the tests
ci: remove Travis-CI configuration
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands