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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update module github.com/golang-migrate/migrate to v4 - autoclosed #20

Closed
wants to merge 1 commit into from
Closed

fix(deps): update module github.com/golang-migrate/migrate to v4 - autoclosed #20

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 19, 2021 •
edited
Loading

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
github.com/golang-migrate/migrate require major v3.5.4+incompatible -> v4.15.1

Release Notes

golang-migrate/migrate

v4.15.1

Compare Source

Changes
Database Drivers
Docker Image
Builds

v4.15.0

Compare Source

Breaking Changes

  • In the Docker image, the location of the migrate binary changed from /usr/local/bin/migrate to /usr/bin/migrate
  • When updating to this version of migrate with postgres, you need to ensure that no migrations are currently running and no old versions of migrate will run at the same time as new versions. The inputs for generating the advisory lock changed so this version will lock with a different key than previous versions.

Changes

Builds
Source Drivers
Database Drivers
CLI
Docs

v4.14.1

Compare Source

Changes

Source Drivers

v4.14.0

Compare Source

Changes

Source Drivers
Database Drivers
CLI
Docs

v4.13.0

Compare Source

Changes

Database Driver
Builds
  • Support Go 1.15 and drop support for Go 1.13
  • Update to golangci-lint v1.30.0
Docs

v4.12.2

Compare Source

Changes

Database Driver
Builds
  • Use make for Docker builds

v4.12.1

Compare Source

Changes

Builds

v4.12.0

Compare Source

Breaking Changes

Changes

Core Library
  • Add multistmt package to handle splitting multiple statements in a migration
Database Driver
Docs
Builds
  • Stop releasing .debs for Ubuntu 18.10 and start releasing for Ubuntu 20.04

v4.11.0

Compare Source

Breaking Changes

Changes

Core Library
Database Driver
  • Properly handle first down migration failures (https://github.com/golang-migrate/migrate/issues/330)
    • Affected drivers: cassandra, cockroachdb, firebird, mysql, neo4j, postgres, ql, redshift, sqlite, and sqlserver
      • Schema migration apply times are now tracked in Neo4j
Source Driver
CLI
Docs

v4.10.0

Compare Source

Changes

Drivers
CLI
Builds
Docs

v4.9.1

Compare Source

Changes

Builds
  • Actually release windows 386

v4.9.0

Compare Source

Changes

Drivers
Builds
Docs

v4.8.0

Compare Source

Changes

Docs
Drivers
  • Add httpfs driver, making it easier to create source drivers that implement thehttp.FileSystem interface. Resolves #​307 thanks to @​fln (#​293).
    • File and GodocVFS sources now use httpfs.PartialDriver
  • Change QL driver from github.com/cznic/ql/driver to modernc.org/ql/driver
Builds
  • Linux ARM binaries are now available with each release thanks to @​pcarranza (#​316)
  • Release now built using Go 1.13

v4.7.1

Compare Source

Changes

v4.7.0

Compare Source

Changes

v4.6.2

Compare Source

Changes

v4.6.1

Compare Source

Changes

v4.6.0

Compare Source

Breaking Changes

Changes

v4.5.0

Compare Source

Breaking Changes

  1. For safety reasons, migrate down now presents a confirmation prompt instead of running all down migrations thanks to @​KlotzAndrew (https://github.com/golang-migrate/migrate/pull/236)
    • For previous behavior, use migrate down -all. Namely, if you have scripts that run migrate down, you'll now have to run migrate down -all

Changes

v4.4.0

Compare Source

Changes

v4.3.1

Compare Source

Changes

v4.3.0

Compare Source

Changes

v4.2.5

Compare Source

Changes

v4.2.4

Compare Source

Changes

v4.2.3

Compare Source

Changes

v4.2.2

Compare Source

Changes

  • Add support for MongoDB migrations thanks to @​bobrovde (#​146)
  • Test improvements
    • MySQL DB driver tests should pass more consistently
  • Update gocql (Cassandra DB driver)
    • Cassandra DB driver tests should pass more consistently

v4.2.1

Compare Source

Changes

  • Fix release packaging issue

v4.2.0

Compare Source

Breaking Changes

  • Update github.com/docker/docker checksum in go.sum which is computed differently in Go 1.11.4
    • If you're using Go modules, you'll need to use Go 1.11.4 with this version.

Changes

v4.1.0

Compare Source

Breaking Changes

  • The Redshift DB driver no longer exposes an embedded database.Driver.
    The decision was made to include this backwards incompatible change since it's unlikely to affect any users. e.g. the affected usage is an anti-pattern
    For more infhttps://github.com/golang-migrate/migrate/pull/128#issuecomment-43617172236171722
    You will not be impacted by this change unless you're using the Redshift DB driver's embedded database.Driver e.g. redshift.Redshift.Driver
    If you encounter this issue, either:
    1. Stop using the embedded database.Driver and instead use the Redshift DB driver which provides the same interface.
    2. Wrap the new Redshift DB driver and update your references to use your new wrapper
  • Debian packages install migrate to /usr/local/bin instead of /usr/bin. You'll need to update any references to the migrate binary that uses absolute paths and ensure that /usr/local/bin is in your environment PATH.

Changes

v4.0.2

Compare Source

Changes

  • Update dependencies

v4.0.1

Compare Source

Changes

v4.0.0

Compare Source

Breaking Changes

  • Opt-in to Go 1.11 modules
    • Per the Go module wiki, only Go 1.9.7+, 1.10.3+, and 1.11+ are supported
    • You'll need to use Go modules to use this release
      • Use modules: go mod init
      • Update to the latest version of migrate: go get -u github.com/golang-migrate/migrate
    • If you're updating from v3.5.2, you'll need to update all of your imports from v3 to v4
      • A command like this should update your imports:
        sed -i -e 's@"github.com/golang-migrate/migrate/v3@​"github.com/golang-migrate/migrate/v4@​g' $(git grep -l '"github.com/golang-migrate/migrate/v3')
    • If you're updating from any other version before v4 except for v3.5.2, you'll need to change your imports to include v4
      • A command like this should update your imports:
        sed -i -e 's@"github.com/golang-migrate/migrate@"github.com/golang-migrate/migrate/v4@​g' $(git grep -l '"github.com/golang-migrate/migrate')
    • Note: BSD sed and GNU sed treat the -i option differently. Please consult your sed man page before running any of the commands above

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch 11 times, most recently from 5ed6a6d to 0dfa89d Compare February 26, 2021 21:52
@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch 19 times, most recently from 9aa4b90 to 2fb25d3 Compare March 6, 2021 08:12
@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch 13 times, most recently from 80df861 to 103c88f Compare April 2, 2021 04:21
@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch from 103c88f to b124367 Compare April 22, 2021 14:19
@renovate
Copy link
Author

renovate bot commented Apr 22, 2021

⚠️ 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 check 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: api/go.sum
Command failed: docker pull docker.io/renovate/go:1.15.11

@renovate renovate bot changed the title Update module github.com/golang-migrate/migrate to v4 fix(deps): update module github.com/golang-migrate/migrate to v4 May 15, 2021
@felixboehm felixboehm closed this May 15, 2021
@renovate
Copy link
Author

renovate bot commented May 15, 2021

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 4.x releases. However, if you upgrade to 4.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@renovate renovate bot deleted the renovate/github.com-golang-migrate-migrate-4.x branch May 15, 2021 15:51
@felixboehm felixboehm restored the renovate/github.com-golang-migrate-migrate-4.x branch May 15, 2021 16:05
@felixboehm felixboehm reopened this May 15, 2021
@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch from b124367 to ed4457c Compare May 15, 2021 16:08
@renovate
Copy link
Author

renovate bot commented May 15, 2021

⚠️ 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 check 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: api/go.sum
Command failed: docker run --rm --name=renovate_go --label=renovate_child -v "/mnt/renovate/gh/advenjourney/advenjourney":"/mnt/renovate/gh/advenjourney/advenjourney" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -v "/tmp/renovate-cache/others/go":"/tmp/renovate-cache/others/go" -e GOPATH -e GOFLAGS -e CGO_ENABLED -w "/mnt/renovate/gh/advenjourney/advenjourney/api" docker.io/renovate/go:1.16.3 bash -l -c "git config --global url.\"https://**redacted**@github.com/\".insteadOf \"https://github.com/\" && go get -d ./... && go mod tidy && go mod tidy"
go: downloading github.com/go-chi/chi v3.3.4+incompatible
go: downloading github.com/lib/pq v1.8.0
go get: added github.com/golang-migrate/migrate v3.5.4+incompatible
github.com/advenjourney/api imports
	github.com/UnnoTed/fileb0x imports
	github.com/UnnoTed/fileb0x/config imports
	gopkg.in/yaml.v2: fstatat /tmp/renovate-cache/others/go/pkg/mod/gopkg.in/yaml.v2@v2.2.8: permission denied

@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch from ed4457c to b3b287d Compare May 15, 2021 21:43
@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch from b3b287d to ea95ebe Compare September 26, 2021 23:10
@renovate renovate bot force-pushed the renovate/github.com-golang-migrate-migrate-4.x branch from ea95ebe to 932a597 Compare October 18, 2021 18:31
@renovate renovate bot changed the title fix(deps): update module github.com/golang-migrate/migrate to v4 fix(deps): update module github.com/golang-migrate/migrate to v4 - autoclosed Mar 7, 2022
@renovate renovate bot closed this Mar 7, 2022
@renovate renovate bot deleted the renovate/github.com-golang-migrate-migrate-4.x branch March 7, 2022 10:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@felixboehm @renovate-bot