Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update spark-core, spark-hive, spark-sql from 3.4.1 to 3.4.2 #815

Merged
merged 1 commit into from
Dec 6, 2023

Conversation

scala-steward
Copy link
Contributor

@scala-steward scala-steward commented Dec 1, 2023

About this PR

πŸ“¦ Updates

from 3.4.1 to 3.4.2

Usage

βœ… Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

πŸ” Files still referring to the old version number

The following files still refer to the old version number (3.4.1).
You might want to review and update them manually.

CHANGELOG.md
README.md
βš™ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.apache.spark" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.spark" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

@scala-steward scala-steward force-pushed the update/spark-core-3.4.2 branch 2 times, most recently from ef6aa8b to 7a99521 Compare December 5, 2023 15:30
@nightscape nightscape merged commit d35d8b4 into nightscape:main Dec 6, 2023
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants