The underlying implementation does not respect the SessionLocker (if one is enabled) and can
be used to check for pending migrations without blocking or being blocked by other operations.
The methods .Up, .UpByOne, and .UpTo from goose.Provider will invoke .HasPending before
acquiring a lock with SessionLocker (if enabled). This addresses an edge case in
Kubernetes-style deployments where newer pods with long-running migrations prevent older pods -
which have all known migrations applied - from starting up due to an advisory lock. For more
details, refer to https://github.com/pressly/goose/pull/507#discussion_r1266498077 and #751.
Move integration tests to ./internal/testing and make it a separate Go module. This will allow
us to have a cleaner top-level go.mod file and avoid imports unrelated to the goose project. See integration/README.md
for more details. This shouldn't affect users of the goose library.
Configuration
📅Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕Ignore: Close this MR and you won't be reminded about this update again.
If you want to rebase/retry this MR, check this box
This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [github.com/pressly/goose/v3](https://github.com/pressly/goose) | require | minor | `v3.19.2` -> `v3.20.0` |
---
### Release Notes
<details>
<summary>pressly/goose (github.com/pressly/goose/v3)</summary>
### [`v3.20.0`](https://github.com/pressly/goose/blob/HEAD/CHANGELOG.md#v3200)
[Compare Source](https://github.com/pressly/goose/compare/v3.19.2...v3.20.0)
- Expand the `Store` interface by adding a `GetLatestVersion` method and make the interface public.
- Add a (non-blocking) method to check if there are pending migrations to the `goose.Provider`
([#​751](https://github.com/pressly/goose/issues/751)):
```go
func (p *Provider) HasPending(context.Context) (bool, error) {}
```
The underlying implementation **does not respect the `SessionLocker`** (if one is enabled) and can
be used to check for pending migrations without blocking or being blocked by other operations.
- The methods `.Up`, `.UpByOne`, and `.UpTo` from `goose.Provider` will invoke `.HasPending` before
acquiring a lock with `SessionLocker` (if enabled). This addresses an edge case in
Kubernetes-style deployments where newer pods with long-running migrations prevent older pods -
which have all known migrations applied - from starting up due to an advisory lock. For more
details, refer to https://github.com/pressly/goose/pull/507#discussion_r1266498077 and [#​751](https://github.com/pressly/goose/issues/751).
- Move integration tests to `./internal/testing` and make it a separate Go module. This will allow
us to have a cleaner top-level go.mod file and avoid imports unrelated to the goose project. See
[integration/README.md](https://github.com/pressly/goose/blob/d0641b5bfb3bd5d38d95fe7a63d7ddf2d282234d/internal/testing/integration/README.md)
for more details. This shouldn't affect users of the goose library.
</details>
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this MR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zMTYuMCIsInVwZGF0ZWRJblZlciI6IjM3LjMxNi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
argoyle
(Migrated from gitlab.com)
merged commit into main2024-04-23 05:42:58 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This MR contains the following updates:
v3.19.2->v3.20.0Release Notes
pressly/goose (github.com/pressly/goose/v3)
v3.20.0Compare Source
Storeinterface by adding aGetLatestVersionmethod and make the interface public.goose.Provider(#751):
The underlying implementation does not respect the
SessionLocker(if one is enabled) and canbe used to check for pending migrations without blocking or being blocked by other operations.
.Up,.UpByOne, and.UpTofromgoose.Providerwill invoke.HasPendingbeforeacquiring a lock with
SessionLocker(if enabled). This addresses an edge case inKubernetes-style deployments where newer pods with long-running migrations prevent older pods -
which have all known migrations applied - from starting up due to an advisory lock. For more
details, refer to https://github.com/pressly/goose/pull/507#discussion_r1266498077 and #751.
./internal/testingand make it a separate Go module. This will allowus to have a cleaner top-level go.mod file and avoid imports unrelated to the goose project. See
integration/README.md
for more details. This shouldn't affect users of the goose library.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this MR and you won't be reminded about this update again.
This MR has been generated by Renovate Bot.