🚨 [security] Update fugit 1.8.1 → 1.11.1 (minor) #6
Conversation
This file contains hidden or 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
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
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?
Security Advisories 🚨
🚨 fugit parse and parse_nat stall on lengthy input
Release Notes
1.11.1 (from changelog)
1.11.0 (from changelog)
1.10.1 (from changelog)
1.10.0 (from changelog)
1.9.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
1.3.4
1.3.3
1.3.2
1.3.1
1.2.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 65 commits:
Avoid requiring files of the gem in Rakefile to avoid redefined method warningsAvoid require in Gemfile & Rakefile to avoid redefined constant warningsAvoid require in *.gemspec files to avoid redefined constant warningsUpdate docs-source/signpost.md1.3.4Check early that $CONCURRENT_JRUBY_HOME is setFix the return value of `Concurrent.available_processor_count` when `cpu.cfs_quota_us` is -1Fix the doc of `Concurrent.available_processor_count`Add `Concurrent.cpu_shares` that is cgroups aware.Update comment for JRuby variant of processor_count to reality1.3.3Improve speed for windows `Get-CimInstance`1.3.2Add a windows job to CIRemove dependency on `win32ole`Automatically run bundle install before running testsRelease edge 0.7.1Make it possible to publish edge without baseEnsure JRuby is used in release testsFix concurrent-ruby-edge to depend on `~> MAJOR.MINOR` of concurrent-rubyGet RakeCompilerDock to work with either podman or docker, based on what is installedFix method name in CHANGELOG.mdPromoting 1.3.1.pre to 1.3.1.Prepare a 1.3.1.pre gem to test things for the 1.3.1 release.Prepare the 1.3.1 release.Prepare the 1.3.0 release.Fix a small grammar issue.Align Java Executor Service behavior for `shuttingdown?`, `shutdown?`Add 10 minute timeout to GitHub ActionsClarifyCleanupsAdd Concurrent.usable_processor_count that is cgroups awareUse 'ruby' for dynamic latest CRuby releaseAdvance "latest" ruby in isolated ci test job to 3.3No continue-on-error for head RubiesBump actions/checkout from 3 to 4Bump actions/deploy-pages from 1 to 4Bump actions/upload-pages-artifact from 1 to 3Fix link label in signpost.mdCI: Tell dependabot to update GH Actions1.2.3Add `TimerTask.new(interval_type:)` option to configure interval calculationdocs: update promises grammar (#1026)docs: fix typo in throttle docs (#1024)Add Ruby 3.3 in CIRemove AtomicReferenceMapBackend and CheapLockableFix some typosFix spurious return in Promises#wait_until_resolvedFix compile error on FreeBSD 14Drop dependency on mutex_mExpose the number of threads that are actively executing tasks with `ThreadPoolExecutor#active_count`. (#1002)Update the list of maintainersAllow TimerTask to be initialized with a specified ExecutorUse executor from arg in then_on/rescue_on/chain_on for PromisesAllow TimerSet to safely handle an executor raising `RejectedExecutionError` (#999)Fix sporadic failures testing with JRuby (#1012)Fix DaemonThreadFactory - reuse single Java thread factoryFix doc typo: yeild → yieldFix broken CI due to rake-compiler error on Ruby < 2.6Fix TimerTask example output (#1003)Fix TimerTask docs to not refer to `#execute` as "blocking" (#996)Fix TimerTask `:execution_interval` docsUpdate comment about ::Array on CRuby, it's not fully thread-safeUpdate comment about ::Hash on CRuby, it's not fully thread-safeCheck the first Concurrent::Map default_proc argument is a Concurrent::Map in more testsCommits
See the full diff on Github. The new version differs by 39 commits:
Release 1.2.11Cache @rweek and @rday, not @refPrepare 1.2.11Release 1.2.10Refine #rweek computation for fugit 96Prepare 1.2.10Streamline credits.mdRelease 1.2.9Compute #rweek from 12:00 not 00:00, gh-38Prepare 1.2.9Group @time and @ref reset in #touch methodTest on Ruby 3.3Reset @time in #incAdapt Makefile to BSD and GNU MakeRelease 1.2.8Cache the @ref time used in #rweek and #rday gh-37Prepare 1.2.82024Merge pull request #36 from floraison/dependabot/github_actions/actions/checkout-4Bump actions/checkout from 3 to 4Cope with EST and EST5EDT on WindowsCope with Europe/KirovStop GH action testing on Rubies < 2.7Drop Gitter link2023Add Ruby 3.2 to GitHub test matrixGo back to EST5EDT for Windows CI :-(Use truffleruby-22.3 in CIAnnotate #rweek and #rdayAdd Igor to creditsMerge pull request #34 from gogainda/patch-1Add TruffleRuby to CIStop testing on win19 + JRuby :-(Avoid jruby-9.2 (404) take 2Avoid jruby-9.2 (goes 404 on GitHub actions :-( )Adapt to GitHub actions 2022-07-04Merge pull request #33 from floraison/dependabot/github_actions/actions/checkout-3Bump actions/checkout from 2 to 3Add .github/dependabot.yml👉 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:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `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