Update bootsnap: 1.4.3 → 1.4.5 (patch) #68
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
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?
✳️ bootsnap (1.4.3 → 1.4.5) · Repo · Changelog
Release Notes
1.4.5 (from changelog)
1.4.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
update changelogbump version to 1.4.5Merge pull request #270 from nalessi/masterUpdate `Bootsnap::LoadPathCache::Store` to better handle concurrent transactions.Merge pull request #267 from kou/ruby-masterAdd support for CRuby 2.7 or laterMerge pull request #261 from jmkim/validate-cache-pathAdd test_helper testMerge pull request #260 from jessetilro/fix-typoFix typo in permission error text.Prepare to 1.4.4Merge pull request #257 from Shopify/rm-disable-iseq-2.5Disable iseq cache in Ruby 2.5Commits
See the full diff on Github. The new version differs by 36 commits:
v1.3.1Merge pull request #172 from gfx/fix_timestamp64_bit_opsfix timestamp64 bit opsMerge pull request #171 from olleolleolle/patch-1Gemspec: drop property rubyforge_projectMerge pull request #170 from wcmonty/wm/fix_namingFix misspelled word: Unpcker -> UnpackerMerge pull request #169 from gfx/make_maint_easymake maintenance easierv1.3.0add tests for actual binary representationsMerge pull request #168 from gfx/timestamp_typedocraise MalformedFormatError for malformed formatre-format by rubocopdo not use Struct for normal classesset rubocop target to disable cops for newer rubiesString#unpack1 is not available before Ruby 2.4commentsmore readable codefix timestamp.rb with suggested changesdo not change bult-in Time class for backward compatibilityremove registering timestamp type for DefaultFactory for nowfix tests: omit nanosecond because its behavior varies in Ruby versionsfix tests: use a fixed time for test fixturecommentsfix use of Time.at for Ruby 2.4 or oldertweaksmap Ruby's Time to MessagePack's timestampstart implementing MessagePack timestamp typev1.2.10Merge pull request #167 from msgpack/static-unpack-ref-optimizewrite_reference_threshold affects only to buffer append which doesn't happen with unpackOptimize MessagePack.unpack to not copy source stringmark osx tests as allow_failures (travis is unstable)try 2.6.1👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.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