Skip to content

build: fix snapshot jobs by not updating @angular/bazel #26357

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

Merged
merged 1 commit into from
Jan 3, 2023

Conversation

devversion
Copy link
Member

Angular Bazel has switched to no longer generate devmode outputs but instead be ESM only. These changes are not yet released, and also they rely on ts_library being patched.

Until our components setup works with it, we cannot update @angular/bazel.

Angular Bazel has switched to no longer generate devmode outputs
but instead be ESM only. These changes are not yet released, and
also they rely on `ts_library` being patched.

Until our components setup works with it, we cannot update
`@angular/bazel`.
@devversion devversion added target: patch This PR is targeted for the next patch release area: build & ci Related the build and CI infrastructure of the project action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 3, 2023
@devversion devversion requested a review from crisbeto January 3, 2023 13:31
@devversion devversion added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jan 3, 2023
@devversion devversion merged commit 0f58252 into angular:main Jan 3, 2023
devversion added a commit that referenced this pull request Jan 3, 2023
Angular Bazel has switched to no longer generate devmode outputs
but instead be ESM only. These changes are not yet released, and
also they rely on `ts_library` being patched.

Until our components setup works with it, we cannot update
`@angular/bazel`.

(cherry picked from commit 0f58252)
@devversion devversion deleted the fix-snapshots-bazel branch January 3, 2023 13:44
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants