-
Notifications
You must be signed in to change notification settings - Fork 46
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
Update dependency io_bazel_rules_docker to v0.25.0 #61
base: master
Are you sure you want to change the base?
Update dependency io_bazel_rules_docker to v0.25.0 #61
Conversation
Can one of the admins verify this patch? |
0dc9fec
to
3e7ec97
Compare
3e7ec97
to
29ee0a4
Compare
29ee0a4
to
a22e6f2
Compare
a22e6f2
to
ea63dd4
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: renovate-bot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ea63dd4
to
f58f15c
Compare
f58f15c
to
e323c05
Compare
e323c05
to
389430c
Compare
389430c
to
1a0f8c7
Compare
1a0f8c7
to
23d5f0d
Compare
23d5f0d
to
187c412
Compare
187c412
to
12d7d0b
Compare
12d7d0b
to
b0a9967
Compare
b0a9967
to
437e06c
Compare
437e06c
to
11a7a64
Compare
11a7a64
to
38d6fc4
Compare
38d6fc4
to
faa8b90
Compare
This PR contains the following updates:
v0.5.1
->v0.25.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
bazelbuild/rules_docker (io_bazel_rules_docker)
v0.25.0
Compare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.25.0
What's Changed
container_image
and its implementation function (#2083) by @lbcjbb in https://github.com/bazelbuild/rules_docker/pull/2084New Contributors
Full Changelog: bazelbuild/rules_docker@v0.24.0...v0.25.0
v0.24.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.24.0
Breaking Changes:
Because of #2042,
toolchain_configure
'sclient_config
becomes a Bazel label instead of an absolute path. Existing applications have to put theirconfig.json
in a Bazel repository, add Bazel rule to export it, and refer it as a label intoolchain_configure
.What's Changed:
v0.23.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.23.0
Breaking Changes
Thanks to @uhthomas we now use Bazel Transitions to request dependencies for the docker target platform. See notes in https://github.com/bazelbuild/rules_docker/pull/1963#issuecomment-997122828 about changes that might be required.
What's Changed
WORKSPACE.bazel
files by @UebelAndre in https://github.com/bazelbuild/rules_docker/pull/1992run_tag
directive. by @psigen in https://github.com/bazelbuild/rules_docker/pull/1995New Contributors
Full Changelog: bazelbuild/rules_docker@v0.22.0...v0.23.0
v0.22.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.22.0
BREAKING CHANGES
Previous releases of rules_docker determined when to make non-deterministic, VCS-stamped outputs based on whether a
{
character appeared in certain attributes. Some rules had a (deprecated)stamp
boolean attribute which affected this behavior all builds of that target. This makes it easy to accidentally bust the Bazel cache, for example a test that depends on acontainer_image
might re-run every time because the image's tag changed with each git SHA.As of this release, you should run
bazel build --stamp
enable stamped outputs.To override this on a single target, the
stamp
attribute on these three rules is now a trinary, just like in other rulesets like rules_pythonstamp = False
you should usestamp = "@​io_bazel_rules_docker//stamp:never"
stamp = True
you should usestamp = "@​io_bazel_rules_docker//stamp:always"
stamp
attribute is given, the default is based on the--[no]stamp
configuration of the build.For more ideas on using this, see the blog post by the author of the stamping PR: https://blog.aspect.dev/stamping-bazel-builds-with-selective-delivery
What's Changed
New Contributors
Full Changelog: bazelbuild/rules_docker@v0.21.0...v0.22.0
v0.21.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.21.0
Changes:
v0.20.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.20.0
Changes:
v0.19.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.19.0
v0.18.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.18.0
Changes:
master
(#1863)01267e6
(#1837)v0.17.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.17.0
Changes:
Update go-containerregsitry dependency to 0.4.1 (#1829)
Fixed some missing digests and addressed other warnings (#1819)
Fixed broken
//tests/docker/util:all
tests (#1817)Update SHA for go-containerregistry (#1815)
Removed
bazel_latest
from default dependencies (#1813)Use actual sha for static:debug image (and update static:latest) (#1804)
make downloading and installing quieter (#1798)
fix the build (#1797)
Revert "Setup assign-size-label action" (#1786)
Introduce github action to mark stale issues/PRs (#1757)
Remove warning about go_image on Mac (#1755)
Add issue and PR templates (#1754)
Revert "Invite maintainers from community (#1750)" (#1753)
Invite maintainers from community (#1750)
Add Domino Data Lab to list of adopters (#1739)
v0.16.0
: 0.16.0Compare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.16.0
Changes:
03c36ef
(#1691)v0.15.0
: Various updates & fixesCompare Source
Copy the following into your WORKSPACE file to use rules_docker at release v0.15.0
Changes:
container_bundle
rule (#1569)v0.14.4
: Numerous additions & fixesCompare Source
v0.14.3
: Numerous additions & fixesCompare Source
Fixes
v0.14.2
: Numerous additions & fixesCompare Source
Fixes
dd7f9c5
(#1433)6e87304
(#1432)7e3bab5
(#1431)70f85ea
(#1426)0366fb2
(#1422)e0dcca4
(#1407)c442972
(#1406)0cb1d71
(#1402)a7a20a0
(#1401)4fefaaa
(#1397)5a55e51
(#1381)v0.14.1
: Fix repro testsCompare Source
Fixes
Fix repro tests (https://github.com/bazelbuild/rules_docker/pull/1379)
v0.14.0
: Numerous additions & fixesCompare Source
Fixes
update rules scala to pick up maven to https change (#1375)
Remote docker host (#1228)
remove par file that was checked in by mistake (#1372)
Get build args from eviron in dockerfile build (#1369)
Path join issues in contrib/dockerfile_build.bzl (#1367)
Update io_bazel_rules_groovy commit hash to
06ce250
(#1368)update rules_groovy call to repositories.bzl (#1366)
Update dependency build_bazel_rules_nodejs to v1.1.0 (#1362)
update puller and loader binaries to pich up #1359 (#1365)
Add http(s)_proxy env var support to puller (#1359)
Use 'portable' mtime as default for tars, like rules_pkg does (#1302)
Update dependency com_github_pkg_errors to v0.9.0 (#1363)
Update dependency io_bazel_rules_go to v0.21.0 (#1364)
Update dependency bazel_toolchains to v2.0.2 (#1361)
Revert "Change to using python 3 in host configuration (#1318)" (#1360)
Change to using python 3 in host configuration (#1318)
Add Canva to adopters list (#1358)
update_deps in Go (#1357)
Update dependency build_bazel_rules_nodejs to v1.0.1 (#1351)
Revert "Add robot_email attr to container push bzl rules (#1353)" (#1355)
Add robot_email attr to container push bzl rules (#1353)
Sync with internal change (#1352)
Update io_bazel_rules_scala commit hash to
bd0c388
(#1348)Update dependency build_bazel_rules_nodejs to v1 ([#1340](https://re
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 PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.