Chore(deps): bump github.com/elastic/package-spec/v3 from 3.0.0-rc1 to 3.0.0 #1507
Conversation
Bumps [github.com/elastic/package-spec/v3](https://github.com/elastic/package-spec) from 3.0.0-rc1 to 3.0.0. - [Release notes](https://github.com/elastic/package-spec/releases) - [Commits](elastic/package-spec@v3.0.0-rc1...v3.0.0) --- updated-dependencies: - dependency-name: github.com/elastic/package-spec/v3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
💔 Build Failed
Failed CI StepsHistory |
|
@aspacca @marc-gr this update is failing because the test package doesn't comply with the new variables for benchmark definitions (changed in elastic/package-spec#639). What would be the required changes in affected packages? Would we also need to include the update of the corpus generator in this PR? (#1491). We have also found out that the |
|
Trying to update all together in #1508. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/go_modules/github.com/elastic/package-spec/v3-3.0.0
branch
Bumps github.com/elastic/package-spec/v3 from 3.0.0-rc1 to 3.0.0.
Commits
eb20617Prepare release 3.0.0 (#646)a4b0a7fBump github.com/elastic/go-elasticsearch/v8 in /compliance (#647)3d00aa2Allow to define number of shards in data stream settings (#645)0998b91Remove deprecatedcorpora.generator.sizein favour of `corpora.gene… (#639)5740417Bump github.com/elastic/elastic-package in /compliance (#643)ac9c24bAllow to define limits of nested and total number of fields per data stream (...708b8a7Bump github.com/elastic/elastic-package in /compliance (#642)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)