Skip to content

build: fix dev bundle location after updating source paths #1735

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
Aug 4, 2022

Conversation

atscott
Copy link
Collaborator

@atscott atscott commented Aug 4, 2022

The dev bundle mapping was broken in
69fad33
but is trivially fixed with this update.

The dev bundle mapping was broken in
angular@69fad33
but is trivially fixed with this update.
@atscott atscott added the target: patch This PR is targeted for the next patch release label Aug 4, 2022
@dylhunn dylhunn self-requested a review August 4, 2022 22:02
@atscott atscott added the action: merge Ready to merge label Aug 4, 2022
@atscott atscott merged commit caa5c25 into angular:main Aug 4, 2022
atscott added a commit that referenced this pull request Aug 4, 2022
The dev bundle mapping was broken in
69fad33
but is trivially fixed with this update.

(cherry picked from commit caa5c25)
@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 Sep 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge Ready to merge 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