Skip to content

Revert: Sandboxes: Use Node 18 to generate Angular prerelease sandboxes#24100

Merged
yannbf merged 3 commits into
nextfrom
revert-24033-fix-angular-prerelease-sandbox
Sep 7, 2023
Merged

Revert: Sandboxes: Use Node 18 to generate Angular prerelease sandboxes#24100
yannbf merged 3 commits into
nextfrom
revert-24033-fix-angular-prerelease-sandbox

Conversation

@kasperpeulen
Copy link
Copy Markdown
Member

Reverts #24033

@kasperpeulen kasperpeulen added build Internal-facing build tooling & test updates ci:daily Run the CI jobs that normally run in the daily job. labels Sep 7, 2023
@yannbf yannbf merged commit 32e8c0b into next Sep 7, 2023
@yannbf yannbf deleted the revert-24033-fix-angular-prerelease-sandbox branch September 7, 2023 16:35
@github-actions github-actions Bot mentioned this pull request Sep 7, 2023
25 tasks
@kasperpeulen kasperpeulen added the patch:yes Bugfix & documentation PR that need to be picked to main branch label Sep 8, 2023
storybook-bot pushed a commit that referenced this pull request Sep 8, 2023
…rerelease-sandbox

Revert: Sandboxes: Use Node 18 to generate Angular prerelease sandboxes
(cherry picked from commit 32e8c0b)
@github-actions github-actions Bot mentioned this pull request Sep 8, 2023
10 tasks
storybook-bot pushed a commit that referenced this pull request Sep 8, 2023
…rerelease-sandbox

Revert: Sandboxes: Use Node 18 to generate Angular prerelease sandboxes
(cherry picked from commit 32e8c0b)
storybook-bot pushed a commit that referenced this pull request Sep 8, 2023
…rerelease-sandbox

Revert: Sandboxes: Use Node 18 to generate Angular prerelease sandboxes
(cherry picked from commit 32e8c0b)
@ndelangen
Copy link
Copy Markdown
Member

Why was this needed?

Could we keep a record of the reason why we revert things in the PR doing the revert?
Do we have an alternate plan?
Will we bring this work back some other time?

@kasperpeulen
Copy link
Copy Markdown
Member Author

kasperpeulen commented Sep 11, 2023

@ndelangen I discussed this with @JReinhold thursday.

It seems that this PR never really worked:
#24033
This is because one job is overriding the other job:
image

We needed to revert this to unblock the daily jobs to release a patch PR.

I think it would be good to re-revert this in a way, that it works, as know the prerelease sandbox is back inDevelopment, and still causing issues in the sandbox workflow.

I first need to some other empathy tasks, but otherwise I will pass this over to the next empathy person.

@github-actions github-actions Bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Sep 11, 2023
@ndelangen ndelangen removed the patch:yes Bugfix & documentation PR that need to be picked to main branch label Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Internal-facing build tooling & test updates ci:daily Run the CI jobs that normally run in the daily job. patch:done Patch/release PRs already cherry-picked to main/release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants