iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/dev-infra/release/BUILD.bazel

23 lines
558 B
Python
Raw Normal View History

build: update to rules_nodejs v4.0.0-beta.0 (#42760) Updates the Bazel NodeJS rules to v4.0.0-beta.0. This is necessary so that the Angular components repo can update, and it's generally good to stay as up-to-date as possible with the Bazel rules as it's easy to fall behind, and updating early allows us to discover issues affecting our tooling earlier (where they are easier to address due to e.g. potential breaking change policy). PR Close #42760
2021-07-06 15:45:55 +02:00
load("//dev-infra:defaults.bzl", "ts_library")
feat(dev-infra): create environment stamping script in ng-dev (#36844) Create a common environment stamping script in the ng-dev tooling as to be used in common release tasks. This is the first step in consolidating pieces of the release scripting process into a single location to develop a release tool. PR Close #36844
2020-04-20 14:44:25 -07:00
ts_library(
name = "release",
srcs = glob([
refactor(dev-infra): move existing env-stamp command into subfolder (#38656) Moves the existing `ng-dev release env-stamp` command into a subfolder so that the staging/publish tool can have its own dedicated folder (without being polluted by the env-stamp logic). Every subcommand should be in its own folder. PR Close #38656
2020-09-09 14:53:13 +02:00
"**/*.ts",
feat(dev-infra): create environment stamping script in ng-dev (#36844) Create a common environment stamping script in the ng-dev tooling as to be used in common release tasks. This is the first step in consolidating pieces of the release scripting process into a single location to develop a release tool. PR Close #36844
2020-04-20 14:44:25 -07:00
]),
visibility = ["//dev-infra:__subpackages__"],
deps = [
feat(dev-infra): add command for building release output (#38656) Adds a command for building all release packages. This command is primarily used by the release tool for building release output in version branches. The release tool cannot build the release packages configured in `master` as those packages could differ from the packages available in a given version branch. Also, the build process could have changed, so we want to have an API for building release packages that is guaranteed to be consistent across branches. PR Close #38656
2020-09-09 14:55:19 +02:00
"//dev-infra/release/build",
feat(dev-infra): add command for printing release train information (#42644) Currently the active release trains are printed when a developer runs `ng-dev publish release`. This is not ideal because it requires the developer to provide an OAuth token, to be on the next branch, and to have no uncommitted changes, while the actual release train information is not dependent on these checks. This commit introduces a new command called `ng-dev release info` that can be used to retrieve relase information without the aforementioned requirements. Note that this command provides more detailed information about release branches than the `ng-dev caretaker check` command (which also requires on authentication as a side note). The `release info` command also prints active LTS branches for example. PR Close #42644
2021-06-24 14:47:11 +02:00
"//dev-infra/release/info",
feat(dev-infra): add release notes generation to ng-dev (#42225) Adds tooling to create ad-hoc release note entries via `ng-dev release notes`. PR Close #42225
2021-05-21 10:49:40 -07:00
"//dev-infra/release/notes",
feat(dev-infra): tool for staging and publishing releases (#38656) Creates a tool for staging and publishing releases as per the new branching and versioning that has been outlined in the following document. The tool is intended to be used across the organization to ensure consistent branching/versioning and labeling: https://docs.google.com/document/d/197kVillDwx-RZtSVOBtPb4BBIAw0E9RT3q3v6DZkykU/edit#heading=h.s3qlps8f4zq7dd The tool implements the actions as outlined in the following initial plan: https://hackmd.io/2Le8leq0S6G_R5VEVTNK9A. The implementation slightly diverged in so far that it performs staging and publishing together so that releasing is a single convenient command. In case of errors for which re-running the full command is not sufficient, we want to consider adding recover functionality. e.g. when the staging completed, but the actual NPM publishing aborted unexpectedly due to build errors. PR Close #38656
2020-09-09 15:01:18 +02:00
"//dev-infra/release/publish",
feat(dev-infra): add release command for setting NPM dist tag (#38656) Introduces a new command for `ng-dev release`, so that the NPM dist tag can be set for all configured NPM packages. This command can be useful in case a manual tag needs to be set, but it is primarily used by the release tooling when a new stable version is cut, and when the previous patch branch needs to be set as LTS version through a `v{major}-lts` dist tag. It is necessary to have this as a command so that the release tool can execute it for old branches where other packages might have been configured. This is similar to the separate `ng-dev build` command that we created. Note that we also added logic for spawning a process conveniently with different "console output" modes. This will be useful for other command invocations in the release tool and it's generally better than directly using native `child_process` as that one doesn't log to the dev-infra debug log file. PR Close #38656
2020-09-09 14:56:58 +02:00
"//dev-infra/release/set-dist-tag",
feat(dev-infra): migrate release tool to use new logging system (#37232) Migrate the release tool in ng-dev to use new logging system rather than directly calling console.* to create a better experience for users. PR Close #37232
2020-05-20 14:55:58 -07:00
"//dev-infra/utils",
feat(dev-infra): support --mode flag for building environment stamp (#40095) When building the environment stamp, support two modes: release and snapshot The release mode will always stamp using the current version of in the root package.json and in snapshot mode will use a version stamp expressing a version based on the tag and the number of commits from the tag. PR Close #40095
2020-12-11 12:34:44 -08:00
"@npm//@types/node",
feat(dev-infra): include experimental version stamp in env stamps (#42934) Include the determined experimental version for stamping in the env stamps created for release and snapshot builds. PR Close #42934
2021-07-22 12:15:50 -07:00
"@npm//@types/semver",
feat(dev-infra): create environment stamping script in ng-dev (#36844) Create a common environment stamping script in the ng-dev tooling as to be used in common release tasks. This is the first step in consolidating pieces of the release scripting process into a single location to develop a release tool. PR Close #36844
2020-04-20 14:44:25 -07:00
"@npm//@types/yargs",
feat(dev-infra): include experimental version stamp in env stamps (#42934) Include the determined experimental version for stamping in the env stamps created for release and snapshot builds. PR Close #42934
2021-07-22 12:15:50 -07:00
"@npm//semver",
feat(dev-infra): create environment stamping script in ng-dev (#36844) Create a common environment stamping script in the ng-dev tooling as to be used in common release tasks. This is the first step in consolidating pieces of the release scripting process into a single location to develop a release tool. PR Close #36844
2020-04-20 14:44:25 -07:00
"@npm//yargs",
],
)
Reference in New Issue Copy Permalink