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

Update dependency data_migrate to v11 #2705

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
data_migrate (source) '~> 9.0' -> '~> 11.0' age adoption passing confidence

Release Notes

ajvargo/data-migrate (data_migrate)

v11.1.0

Compare Source

v11.0.0

Compare Source

v9.4.2

Compare Source

  • Fix db:prepare:with_data task

v9.4.1

Compare Source

  • Add db:prepare task

v9.4.0

Compare Source

v9.3.0

Compare Source

v9.2.0

Compare Source

v9.1.3

Compare Source

What's Changed

Full Changelog: ilyakatz/data-migrate@9.1.2...9.1.3

v9.1.2

Compare Source

What's Changed

Full Changelog: ilyakatz/data-migrate@v9.1.1...9.1.2

v9.1.1

Compare Source

What's Changed

v9.1.0

Compare Source

  • Fix a bug that caused schema_sha1 in ar_internal_metadata to be reset to the data_schema.rb file. (#​272)
  • Remove the need for empty data_schema files for non-primary databases. (#​273)

Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Nov 4, 2024
@renovate renovate bot force-pushed the renovate/data_migrate-11.x branch 2 times, most recently from 1e20032 to 87fdc57 Compare November 8, 2024 10:55
@renovate renovate bot changed the title Update dependency data_migrate to v11 chore(deps): update dependency data_migrate to v11 Nov 8, 2024
@renovate renovate bot force-pushed the renovate/data_migrate-11.x branch 5 times, most recently from d6c1709 to c311154 Compare November 14, 2024 08:30
@renovate renovate bot force-pushed the renovate/data_migrate-11.x branch 2 times, most recently from 60a722c to bf4497c Compare November 19, 2024 08:52
Copy link
Contributor Author

renovate bot commented Nov 19, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile.lock
[11:32:46.508] INFO (959): Installing tool [email protected]...
installing v2 tool ruby v3.0.3
/usr/local/containerbase/tools/v2/ruby.sh: line 82: /etc/gemrc: Permission denied
[11:32:46.660] ERROR (959): Command failed with exit code 1: /usr/local/containerbase/bin/install-tool.sh ruby 3.0.3
[11:32:46.661] FATAL (959): Install tool ruby failed in 157ms.


@renovate renovate bot force-pushed the renovate/data_migrate-11.x branch from bf4497c to a0c5758 Compare November 26, 2024 11:32
@renovate renovate bot changed the title chore(deps): update dependency data_migrate to v11 Update dependency data_migrate to v11 Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants