Update Everything (major) #5243
Closed
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-everything
branch
from
7fbc14e to
37bb0ad
Compare
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.
This PR contains the following updates:
0.8.0->1.0.20.38.1->1.5.0v0.0.0->v1.0.1v0.0.0->v2.1.1v0.0.0->v1.1.1v0.0.0->v1.7.1v0.0.0->v1.0.0v0.0.0->v1.0.0v0.0.0->v1.8.0v0.0.0->v2.2.8v0.0.0->v1.4.3v0.0.0->v1.1.1v0.0.0->v1.4.2v0.0.0->v1.2.0v0.0.0->v1.2.0v0.0.0->v1.0.0v0.0.0->v1.0.0v0.0.0->v1.0.0v0.0.0->v1.0.0v0.0.0->v2.0.3v0.0.0->v1.0.6v0.0.0->v1.0.2v0.0.0->v1.1.6v0.0.0->v1.0.2v0.0.0->v1.3.4v0.0.0->v1.0.1v0.0.0->v1.0.1v0.0.0->v1.1.3v0.0.0->v1.1.0v0.0.0->v2.1.0v0.0.0->v1.2.0v0.0.0->v1.5.1v0.0.0->v1.7.0v0.0.0->v1.5.0v0.0.0->v1.1.0v0.0.0->v1.0.5v0.0.0->v1.0.0v0.0.0->v1.1.1v0.0.0->v1.1.0v0.0.0->v2.0.2v0.0.0->v1.1.2v0.0.0->v1.9.2v0.0.0->v1.0.0v0.0.0->v2.0.0v0.0.0->v2.0.0v0.0.0->v1.7.1v0.0.0->v1.6.1v0.0.0->v2.0.0v0.0.0->v1.0.0v0.0.0->v1.2.8v0.0.0->v1.14.3v0.0.0->v1.2.1v0.0.0->v2.2.8v0.0.0->v12.0.0v0.0.0->v1.0.0v0.0.0->v1.2.0v0.0.0->v1.3.0Release Notes
bazelbuild/bazel-skylib
v1.0.2Compare Source
New Features
Incompatible Changes
Added types.is_set() to test whether an arbitrary object is a set as defined by sets.bzl.
WORKSPACE setup
Using the rules
See the source.
v1.0.1Compare Source
New Features
Patch release to 1.0.0 to provide toolchain for unittest library.
WORKSPACE setup
Using the rules
See the source.
v1.0.0Compare Source
WARNING - unittests do not work. Wait for 1.0.1
Incompatible Changes
via @bazel_skylib//lib:.bzl.
New Features
WORKSPACE setup
Using the rules
See the source.
v0.9.0Compare 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
bazelbuild/rules_nodejs
v1.5.0Compare Source
Bug Fixes
closes #1606
Features
Examples
Documentation
1.4.1 (2020-03-06)
Bug Fixes
v1.4.1Compare Source
Bug Fixes
v1.4.0Compare Source
Bug Fixes
Features
argsattribute to rollup_bundle rule (#1681) (94c6182)v1.3.0Compare Source
Bug Fixes
Features
@npm//foo__all_filesfilegroup that includes all files in the npm package (#1600) (8d77827)1.2.4 (2020-01-31)
Bug Fixes
1.2.2 (2020-01-31)
Bug Fixes
Code Refactoring
Examples
1.2.1 (2020-01-30)
Bug Fixes
v1.2.4Compare Source
Bug Fixes
v1.2.2Compare Source
Bug Fixes
Code Refactoring
Examples
v1.2.1Compare Source
Bug Fixes
v1.2.0Compare Source
Bug Fixes
Features
v1.1.0Compare Source
Bug Fixes
Features
1.0.1 (2020-01-03)
Bug Fixes
Features
v1.0.1Compare Source
Bug Fixes
Features
v1.0.0Compare Source
Bug Fixes
chore
Code Refactoring
bootstrapattribute & fix $(location) expansions in nodejs_binary templated_args (1860a6a)argsto yarn_install & npm_install (#1462) (d245d09)Features
Performance Improvements
BREAKING CHANGES
templated_args_fileremoved from nodejs_binary, nodejs_test & jasmine_node_test. This was a separation of concerns and complicated node.bzl more than necessary while also being rigid in how the params file is formatted. It is more flexible to expose this functionality as another simple rule named params_file.To match standard$(location) and $ (locations) expansion, params_file args location expansions are also in the standard short_path form (this differs from the old templated_args behavior which was not Bazel idiomatic)
Usage example:
This can be replaced with the
--node_options=--require=$(location label)argument such as,or
templated_args$(location)and$(locations)are now correctly expanded when there is no space before$(locationsuch as
templated_args = ["--node_options=--require=$(rlocation $(location :bootstrap.js))"].Path is returned in runfiles manifest path format such as$(mlocation) and $ (mlocations) used to expand
repo/path/to/file. This differs from how $(location)and $(locations) expansion behaves in expansion the
argsattribute of a __binary or __test which returnsthe runfiles short path of the format
./path/to/filefor user repo and../external_repo/path/to/filefor externalrepositories. We may change this behavior in the future with
to the runfiles manifest path.
See https://docs.bazel.build/versions/master/be/common-definitions.html#common-attributes-binaries.
argsin yarn_install and npm_install can be used to pass arbitrary arguments so we removed the following attributes:npm_packagerenamed topkg_npm. This is to match the naming convention for package rules https://docs.bazel.build/versions/master/be/pkg.html.//internal/common:npm_pacakge_info.bzl removed; load from //:providers.bzl instead
transitive_js_ecma_script_module_info macro removed; use js_ecma_script_module_info instead
@npm_bazel_karma//:browser_repositories.bzl removed; use @io_bazel_rules_webtesting//web/versioned:browsers-0.3.2.bzl instead
@npm_bazel_protractor//:browser_repositories.bzl removed; use @io_bazel_rules_webtesting//web/versioned:browsers-0.3.2.bzl instead
ts_web_test & ts_web_test_suite marcos removed; use karma_web_test & karma_web_test_suite instead
0.42.3 (2019-12-10)
To upgrade:
and run
yarn upgrade --scope @​bazelto 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
0.42.2 (2019-12-04)
Bug Fixes
0.42.1 (2019-11-27)
To upgrade:
and run
yarn upgrade --scope @​bazelto 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_devserverandpkg_webbut 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_binand 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=Trueand you can now use
$@​to refer to the location of a single outputv0.42.3Compare Source
To upgrade:
and run
yarn upgrade --scope @​bazelto 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.2Compare Source
Bug Fixes
v0.42.1Compare Source
To upgrade:
and run
yarn upgrade --scope @​bazelto 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_devserverandpkg_webbut 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_binand 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=Trueand you can now use
$@​to refer to the location of a single outputv0.42.0Compare Source
This release had a bug, see 0.42.1 instead
https://github.com/bazelbuild/rules_nodejs/releases/tag/0.42.1
v0.41.0Compare Source
To upgrade:
and run
yarn upgrade --scope @​bazelto 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_packagerule has been renamed topkg_weband is now a public APIUpdate your load statements from
to
ts_devserverandpkg_web(previouslyweb_package) no longer have anindex_htmlattribute.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_htmlrule 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-win10saucelabs 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=1is no longer functional to request debugging outputs. Use-c dbginstead (this matches Bazel's behavior for C++).We renamed some of the generated targets in the
@nodejs//workspace:bazel run @​nodejs//:npmis replaced withbazel run @​nodejs//:npm_node_repositoriesandbazel run @​nodejs//:yarnis replaced withbazel run @​nodejs//:yarn_node_repositories.@nodejs//:yarnand@nodejs//:npmnow run yarn & npm in the current working directory instead of on all of thepackage.jsonfiles innode_repositories().@nodejs//:bin/node&@nodejs//:bin/node.cmd(on Windows) are no longer valid targets. Use@nodejs//:nodeinstead 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//:yarninstead 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//:npminstead 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.0Compare Source
Bug Fixes
Features
argsattribute to support additional command line arguments (563bad7)0.39.1 (2019-10-29)
Bug Fixes
Features
v0.39.1Compare Source
Bug Fixes
Features
v0.39.0Compare Source
Bug Fixes
Code Refactoring
Features
Renovate configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Enabled.
♻️ 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 WhiteSource Renovate. View repository job log here.