[ruby] Update faker 1.8.7 → 3.4.2 (major) #391
Closed
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
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?
✳️ faker (1.8.7 → 3.4.2) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
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 55 commits:
1.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 testsRelease Notes
1.14.5
1.14.4
1.14.3
1.14.1
1.14.0
1.13.0
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.
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