Update dependency bazel_skylib - autoclosed #3
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.
This PR contains the following updates:
0.5.0
->0.9.0
0.3.1
->0.42.3
0.6.1
->0.23.2
0.0.3
->0.1.0
Release Notes
bazelbuild/bazel-skylib
v0.9.0
Compare Source
Incompatible Changes
old_sets.bzl should be removed in a following skylib release.
New Features
common_settings.bzl: Standard data types for user defined build
configuration. Common scalar build settings for rules to use so they don't
recreate them locally. This fulfills part of the SBC design doc:
https://docs.google.com/document/d/1vc8v-kXjvgZOdQdnxPTaV0rrLxtP2XwnD2tAZlYJOqw/edit#bookmark=id.iiumwic0jphr
selects.bzl: Add config_setting_group for config_setting AND/OR-chaining
Implements
https://github.com/bazelbuild/proposals/blob/master/designs/2018-11-09-config-setting-chaining.md.
run_binary: runs an executable as an action
desired arguments, environment, inputs, and outputs, as a single build
action, without shelling out to Bash.
New
native_binary()
andnative_test()
rules let you wrap a pre-builtbinary in a binary and test rule respectively.
interface. Rules like genrule can tool-depend on it, and it can be
executed with "bazel run". This rule can also augment the binary with
runfiles.
binary rule.
diff_test: test rule compares two files and passes if the files match.
maprule: move functionality to maprule_util.bzl.
maprule_util.bzl will benefit planned new rules (namely a genrule alternative).
This release is tested with Bazel 0.28
WORKSPACE setup
v0.8.0
Compare Source
New Features
analysis_test
rule to verify that targets under test pass Bazel’s analysis phase. This is similar to the existingbuild_test
rule, except that actions of the underlying targets are not executed. See documentation.write_file
rule to write UTF-8 encoded text files. (Works for bash platforms and Windows)copy_file
rule to copy a file to another location. (Works for bash platforms and Windows)dicts.add()
now accepts kwargs to add to the resulting dict.This release is tested with Bazel 0.23
Thanks to the following external contributors:
Please use the
bazel-skylib.0.8.0.tar.gz
release asset from your BazelWORKSPACE
.SHA-256 digest:
2ef429f5d7ce7111263289644d233707dba35e39696377ebab8b0bc701f7818e
[Complete list of changes](
v0.7.0
Compare Source
Incompatible Changes
unittest.bzl
requiring minor migration effort:Test implementation functions for this framework now must return the result of
unittest.end(env)
instead of simply invoking this method. That is:def _your_test(ctx):
env = unittest.begin(ctx)
Assert statements go here
Assert statements go here
New Features
Added Windows support for
unittest.bzl
.Added maprule rules (
cmd_maprule
andbash_maprule
under//rules/maprule.bzl
for Windows and bash support, respectively)Added a
build_test
rule (build_test
under//rules/build_test.bzl
) to create test targets that verify that other targets build. Note that this rule does not currently work on Windows (though support for Windows shall come at a later time).v0.6.0
Compare Source
Renamed several instances of "Skylark". The old label and symbol names remain as aliases to these new locations and names temporarily. The aliases will go away on a future release.
//:skylark_library.bzl
renamed to//:bzl_library.bzl
skylark_library
renamed tobzl_library
SkylarkLibraryInfo
renamed toStarlarkLibraryInfo
//:lib.bzl
has been deprecated. Depend directly on the bazel-skylib modules you need instead of depending onlib.bzl
.//:sets.bzl
has been deprecated. Depend instead on//:new_sets.bzl
, which was introduced in version 0.4.0 and has better performance thansets.bzl
.sets.bzl
will be removed in a future release.Updated Starlark code to be compatible with Bazel version 0.19.2
bazelbuild/rules_nodejs
v0.42.3
Compare Source
To upgrade:
and run
yarn upgrade --scope @​bazel
to update all your@bazel
-scoped npm packages to the latest versions.(or manually do the npm equivalent - they don't have a way to update a scope)
Bug Fixes
Features
v0.42.2
Compare Source
Bug Fixes
v0.42.1
Compare Source
To upgrade:
and run
yarn upgrade --scope @​bazel
to update all your@bazel
-scoped npm packages to the latest versions.(or manually do the npm equivalent - they don't have a way to update a scope)
New stuff
In 0.41.0 we noted that a feature for inserting
<script>
and<link>
tags was dropped fromts_devserver
andpkg_web
but the replacement wasn't available. Now it is thanks to @jbedard who published a standalone npm packagehtml-insert-assets
. You can see how it's wired in the examples.If you waited to upgrade before, now you should.
Bug Fixes
BREAKING CHANGES
npm_package_bin
and all rules generated by it, to match genrule behavior as documented at https://docs.bazel.build/versions/master/be/make-variables.html#predefined_genrule_variablesThis means that usage of the
$@​
shortcut to refer to the output directory should now be$(@​D)
whenoutput_dir=True
and you can now use
$@​
to refer to the location of a single outputv0.42.0
Compare Source
This release had a bug, see 0.42.1 instead
https://github.com/bazelbuild/rules_nodejs/releases/tag/0.42.1
v0.41.0
Compare Source
To upgrade:
and run
yarn upgrade --scope @​bazel
to update all your@bazel
-scoped npm packages to the latest versions.(or manually do the npm equivalent - they don't have a way to update a scope)
BREAKING CHANGES
As mentioned before, we are close to a 1.0 release, so we are making all our breaking changes now to prepare for a period of stability. Sorry for the long list this time!
web_package
rule has been renamed topkg_web
and is now a public APIUpdate your load statements from
to
ts_devserver
andpkg_web
(previouslyweb_package
) no longer have anindex_html
attribute.They expect an index.html file to be among the assets, and to already
have the script and link tags needed for the app to work.
The feature where those tags were injected into the html dynamically has
been moved to its own rule, inject_html.
We are in a transition state where the
inject_html
rule is not published, because we want this to be a plain npm package and not Bazel-specific. We will publish this functionality soon. If you depend on it, you may want to delay this upgrade.internal/rollup_bundle rule is removed. see https://github.com/bazelbuild/rules_nodejs/wiki for migration instructions
Removed the expand_location_into_runfiles helper from //internal:node.bzl
Load it from //internal/common:expand_into_runfiles instead
npm karma deps for karma_web_test and karma_web_suite are now peer deps so that the versions used can be chosen by the user.
This PR also removes the built-in
@io_bazel_rules_webtesting//browsers/sauce:chrome-win10
saucelabs support. It is not very useful as it only tests a single browser and it difficult to use. In the angular repo, saucelabs support was implemented with a custom karma config using karma_web_test. This is the recommended approach.--define=DEBUG=1
is no longer functional to request debugging outputs. Use-c dbg
instead (this matches Bazel's behavior for C++).We renamed some of the generated targets in the
@nodejs//
workspace:bazel run @​nodejs//:npm
is replaced withbazel run @​nodejs//:npm_node_repositories
andbazel run @​nodejs//:yarn
is replaced withbazel run @​nodejs//:yarn_node_repositories
.@nodejs//:yarn
and@nodejs//:npm
now run yarn & npm in the current working directory instead of on all of thepackage.json
files innode_repositories()
.@nodejs//:bin/node
&@nodejs//:bin/node.cmd
(on Windows) are no longer valid targets. Use@nodejs//:node
instead on all platforms. You can still call the old targets in their platform specific node repositories such as@nodejs_darwin_amd64//:bin/node
.@nodejs//:bin/yarn
&@nodejs//:bin/yarn.cmd
(on Windows) are no longer valid targets. Use@nodejs//:yarn
instead on all platforms. You can still call the old targets in their platform specific node repositories such as@nodejs_darwin_amd64//:bin/yarn
.@nodejs//:bin/npm
&@nodejs//:bin/npm.cmd
(on Windows) are no longer valid targets. Use@nodejs//:npm
instead on all platforms. You can still call the old targets in their platform specific node repositories such as@nodejs_darwin_amd64//:bin/npm
.Bug Fixes
chore
Code Refactoring
Features
v0.40.0
Compare Source
Bug Fixes
Features
args
attribute to support additional command line arguments (563bad7)0.39.1 (2019-10-29)
Bug Fixes
Features
v0.39.1
Compare Source
Bug Fixes
Features
v0.39.0
Compare Source
Bug Fixes
Code Refactoring
Features
BREAKING CHANGES
in favor of declaring needed packages in the deps/data of the rule that
invokes the tool.
0.38.3 (2019-10-11)
Bug Fixes
Features
0.38.2 (2019-10-09)
Bug Fixes
Features
0.38.1 (2019-10-03)
Bug Fixes
Features
v0.38.3
Compare Source
Bug Fixes
Features
v0.38.2
Compare Source
Bug Fixes
Features
v0.38.1
Compare Source
Bug Fixes
Features
v0.38.0
Compare Source
Bug Fixes
chore
Code Refactoring
Features
BREAKING CHANGES
index.bzl instead.
The @yarn workspace is no longer created. Use @nodejs//:yarn instead.
To use them, first install the http-server and/or history-server packages
Then load("@npm//http-server:index.bzl", "http_server")
(or replace with history-server, noting that the rule has underscore where the package has hyphen)
0.37.1 (2019-09-16)
Bug Fixes
Features
v0.37.1
Compare Source
Bug Fixes
Features
v0.37.0
Compare Source
Bug Fixes
chore
Features
BREAKING CHANGES
0.36.2 (2019-08-30)
Bug Fixes
Features
0.36.1 (2019-08-20)
Features
v0.36.2
Compare Source
Bug Fixes
Features
v0.36.1
Compare Source
Features
v0.36.0
Compare Source
Bug Fixes
Features
jasmine_config
(715ffc6)v0.35.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
jasmine: You can no longer get jasmine_node_test from @build_bazel_rules_nodejs.
Use
load("@​npm_bazel_jasmine//:index.bzl", "jasmine_node_test")
instead
You need to remove
@npm//jasmine
from the deps of thejasmine_node_test
If you use user-managed dependencies, see the commit for examples of
the change needed
Also makes the repo bazel-lint-clean, so running yarn bazel:lint-fix no
longer makes edits.
v0.34.0
Compare Source
Bug Fixes
Features
0.33.1 (2019-07-12)
Bug Fixes
v0.33.1
Compare Source
Bug Fixes
v0.33.0
Compare Source
Bug Fixes
Features
0.32.2 (2019-06-21)
Bug Fixes
0.32.1 (2019-06-19)
Bug Fixes
v0.32.2
Compare Source
Bug Fixes
v0.32.1
Compare Source
Bug Fixes
v0.32.0
Compare Source
Bug Fixes
Features
v0.31.1
[Compare Source](https://togithub.com/ba
Configuration
📅 Schedule: 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.