andygrove opened a new pull request, #323:
URL: https://github.com/apache/datafusion-spark/pull/323

   ## Which issue does this PR close?
   
   Part of #56: the "Add a Dependabot configuration" item.
   
   ## Rationale for this change
   
   Nothing keeps the Cargo dependencies or the GitHub Actions in our workflows 
up to date. apache/datafusion and apache/datafusion-iceberg both use Dependabot 
for this.
   
   ## What changes are included in this PR?
   
   A `.github/dependabot.yml`, based on apache/datafusion-iceberg's:
   
   - **Cargo**, checked weekly.
     - Minor and patch updates are grouped into one pull request.
     - Major updates of `datafusion*` and `arrow*` are ignored. Under the 
versioning policy proposed in #319, `datafusion-spark` 56.x stays on DataFusion 
56 and the `arrow` version it uses, so those major versions change only when 
`main` moves to the next DataFusion major version.
     - DataFusion is a git dependency on `branch-56` for now, so Dependabot can 
only update its locked commit.
   - **GitHub Actions**, checked weekly and grouped into one pull request.
   - **pip is left out on purpose.** 
`crates/sqllogictest/scripts/requirements.txt` pins `pyspark==4.2.0`, the Spark 
version the sqllogictest files are checked against. Changing it is a decision, 
not a routine update.
   
   There are no `labels`, because this repository has no `auto-dependencies` 
label yet.
   
   ## Are these changes tested?
   
   The file is valid YAML and follows apache/datafusion-iceberg's working 
configuration. GitHub validates `dependabot.yml` once it is on the default 
branch, and reports any errors in the repository's Dependabot settings.
   
   ## Are there any user-facing changes?
   
   No.
   
   _This PR was written by an LLM (Claude) and reviewed before opening._
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to