-
Notifications
You must be signed in to change notification settings - Fork 440
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
Bump github.com/elastic/elastic-package from 0.38.0 to 0.40.0 #2845
Bump github.com/elastic/elastic-package from 0.38.0 to 0.40.0 #2845
Conversation
Bumps [github.com/elastic/elastic-package](https://github.com/elastic/elastic-package) from 0.38.0 to 0.40.0. - [Release notes](https://github.com/elastic/elastic-package/releases) - [Changelog](https://github.com/elastic/elastic-package/blob/main/.goreleaser.yml) - [Commits](elastic/elastic-package@v0.38.0...v0.40.0) --- updated-dependencies: - dependency-name: github.com/elastic/elastic-package dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
github.com/elastic/go-licenser v0.4.0 // indirect | ||
github.com/elastic/go-sysinfo v1.7.1 // indirect | ||
github.com/elastic/go-ucfg v0.8.4 // indirect | ||
github.com/elastic/go-windows v1.0.1 // indirect | ||
github.com/elastic/package-spec v1.4.1 // indirect | ||
github.com/elastic/package-spec v1.6.0 // indirect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤞
Many numbers have changed their format in the golden files, I guess that this is caused by elastic/elastic-package#717. The question would be if the current format is the good one 🤔 |
Most of them seem correct:
|
When I was working on elastic/elastic-package#717 I wrote a checker to find packages that would fail the new tests (code here). This is the output from running it on a987263.
|
…stic-package-0.40.0
I will just merge this one :) |
…c#2845) * Bump github.com/elastic/elastic-package from 0.38.0 to 0.40.0 Bumps [github.com/elastic/elastic-package](https://github.com/elastic/elastic-package) from 0.38.0 to 0.40.0. - [Release notes](https://github.com/elastic/elastic-package/releases) - [Changelog](https://github.com/elastic/elastic-package/blob/main/.goreleaser.yml) - [Commits](elastic/elastic-package@v0.38.0...v0.40.0) --- updated-dependencies: - dependency-name: github.com/elastic/elastic-package dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * Regenerate expected files * Update more files Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jaime Soriano Pastor <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Bumps github.com/elastic/elastic-package from 0.38.0 to 0.40.0.
Release notes
Sourced from github.com/elastic/elastic-package's releases.
Commits
9a0c866
Chore(deps): bump k8s.io/apimachinery from 0.23.4 to 0.23.5 (#738)dc23c4b
Write migration docs to publish packages to v2 (#728)f8f678d
Implement minimal pipeline to publish a package (#731)e28b434
Chore(deps): bump github.com/stretchr/testify from 1.7.0 to 1.7.1 (#737)bdcca3c
Chore(deps): bump github.com/magefile/mage from 1.11.0 to 1.13.0 (#736)3ba6d95
Chore(deps): bump github.com/elastic/package-spec from 1.5.0 to 1.6.0 (#735)648451a
Chore(deps): bump golang.org/x/tools from 0.1.9 to 0.1.10 (#734)e3841a7
internal/testrunner/runners/pipeline: unmarshal test results using UseNumber ...99cfd37
Fix: jenkins.JenkinsException: create[Ingest-manager/elastic-package/package-...8a8e3d2
Define minimal publishing pipeline (#729)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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)