Bump bootsnap from 1.16.0 to 1.18.3 in /back

[dependabot[bot]]

Bumps bootsnap from 1.16.0 to 1.18.3.

Changelog

Sourced from bootsnap's changelog.

1.18.3

• Fix the cache corruption issue in the revalidation feature. See #474. The cache revalidation feature remains opt-in for now, until it is more battle tested.

1.18.2

• Disable stale cache entries revalidation by default as it seems to cause cache corruption issues. See #471 and #474. Will be re-enabled in a future version once the root cause is identified.
• Fix a potential compilation issue on some systems. See #470.

1.18.1

• Handle EPERM errors when opening files with O_NOATIME.

1.18.0

• Bootsnap.instrumentation now receive :hit events.
• Add Bootsnap.log_stats! to print hit rate statistics on process exit. Can also be enabled with BOOTSNAP_STATS=1.
• Revalidate stale cache entries by digesting the source content. This should significantly improve performance in environments where mtime isn't preserved (e.g. CI systems doing a git clone, etc). See #468.
• Open source files and cache entries with O_NOATIME when available to reduce disk accesses. See #469.
• bootsnap precompile --gemfile now look for .rb files in the whole gem and not just the lib/ directory. See #466.

1.17.1

• Fix a compatibility issue with the prism library that ships with Ruby 3.3. See #463.
• Improved the Kernel#require decorator to not cause a method redefinition warning. See #461.

1.17.0

• Ensure $LOAD_PATH.dup is Ractor shareable to fix an conflict with did_you_mean.
• Allow to ignore directories using absolute paths.
• Support YAML and JSON CompileCache on TruffleRuby.
• Support LoadPathCache on TruffleRuby.

Commits

• 48c08b0 Release 1.18.3
• 08cd0d9 Merge pull request #476 from Shopify/fix-revalidation
• ad189d1 Fix a cache corruption issue during revalidation
• 2dba040 Release 1.18.2
• 38554bb Merge pull request #475 from Shopify/disable-revalidation-by-default
• a5b46d0 Disable stale cache entries revalidation by default
• 4b6d40e Merge pull request #473 from Shopify/gnu-source
• 33754b4 Define _GNU_SOURCE properly
• d4b4666 Workaround fdatasync bug on macOS
• c88b4bd Include errno_provenance in sys_err messages
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cl-dev-bot]

	Warnings
:warning:	The PR title contains no Jira issue key (case-sensitive)
:warning:	The branch name contains no Jira issue key (case-sensitive)

	Messages
:book:	Changelog provided 🎉
:book:	Run the e2e tests
:book:	Check translation progress

Generated by :no_entry_sign: dangerJS against 545ffd7ccf746099594dd16ec86e8fa9b41be98c

[dependabot[bot]]

Looks like bootsnap is up-to-date now, so this is no longer needed.