build: remove legacy release tooling #23428
Merged
Conversation
This file contains hidden or 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
Removes the legacy release tooling from the repository. We had two successful releases with the new tool, and the tool has been used for quite a while in the framework repository. We will fix issues in the new release tool going forward.
devversion
added
merge safe
target: patch
google-cla
bot
added
the
cla: yes
amysorto
added
target: major
devversion
added a commit
to devversion/material2
that referenced
this pull request
Aug 25, 2021
Removes the legacy release tooling from the repository. We had two successful releases with the new tool, and the tool has been used for quite a while in the framework repository. We will fix issues in the new release tool going forward.
amysorto
pushed a commit
that referenced
this pull request
Aug 25, 2021
* build: update shared dev-infra package Updates the shared dev-infra package to take advanatge of recent improvements for the release tool. This also fixes the issue where the merge tooling requires the `breaking change` label, while there also is the `state: breaking change` label. The ng-dev tool no longer accepts custom configuration of that label. Also the merge configuration no longer accepts custom labels, in order to achieve consistent labeling as specified in the Angular versioning/branching/labeling spec. * build: check .ng-dev tool configuration in CI Checks the `.ng-dev` tool configuration in CI, compared to doing it locally when the caretaker intends to perform a merge and then realizes the config is broken. * build: remove legacy release tooling (#23428) Removes the legacy release tooling from the repository. We had two successful releases with the new tool, and the tool has been used for quite a while in the framework repository. We will fix issues in the new release tool going forward. * build: no longer install snapshot build of `@angular/bazel` No longer uses a snapshot build for `@angular/bazel`. We previously used a snapshot build in order to update to v4 of `rules_nodejs`. * build: add missing dependency for jsonc-parser Sets up the jsonc-parser dependency in the BUILD bazel file.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Removes the legacy release tooling from the repository. We
had two successful releases with the new tool, and the tool
has been used for quite a while in the framework repository.
We will fix issues in the new release tool going forward.