Bump libcnb and libherokubuildpack from 0.6.0 to 0.7.0 #60
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
@dependabot rebase |
Bumps [libcnb](https://github.com/heroku/libcnb.rs) from 0.6.0 to 0.7.0. - [Release notes](https://github.com/heroku/libcnb.rs/releases) - [Commits](heroku/libcnb.rs@libcnb/v0.6.0...libcnb/v0.7.0) --- updated-dependencies: - dependency-name: libcnb dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/cargo/libcnb-0.7.0
branch
from
8c77437 to
4d25f9d
Compare
Bumps libherokubuildpack from 0.6.0 to 0.7.0. --- updated-dependencies: - dependency-name: libherokubuildpack dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
edmorley
changed the title
Since: - that's what's tested in CI (which uses latest stable) - it helps remind people to upgrade locally - libherokubuildpack has a minimum of 1.60 anyway
Since for libcnb* releases we tend to manually trigger anyway, and weekly reduces the noise over daily slightly (not that there are many PRs for this repo, but in case that changes in the future).
Since: - this is a framework change rather than a test/dev dependency - otherwise the "unreleased" section is empty, which looks stranage if a release is performed
edmorley
approved these changes
Apr 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps libcnb from 0.6.0 to 0.7.0.
Release notes
Sourced from libcnb's releases.
Commits
4e3168aPrepare new release of all crates (#391)f94eb8aBump Swatinem/rust-cache from 1.3.0 to 1.4.0 (#392)adc886fUpdate bollard requirement from 0.11.1 to 0.12.0 (#390)553116aAdd CODEOWNERS file (#389)0afba2aReplace malax/libcnb.rs with heroku/libcnb.rs (#388)70fcf6aAdd explicit error for missing exec.d paths (#387)9144abaOnly create layerenvdirectories if env vars are being written (#385)06b33ccMerge pull request #382 from Malax/build-plan-refactor18b93d1more fixes887a754Refactor impl From<String> for RequireDependabot 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 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)