next.js
[release-legacy] fix: set `stable` dist tag for backport releases instead of `latest`
#79596

Merged

[release-legacy] fix: set `stable` dist tag for backport releases instead of `latest` #79596

devjiwonchoi merged 2 commits into canary from jiwon/05-24-_release-legacy_fix_backport_release_dist_tag_is_latest_

[release-legacy] fix: backport release dist tag is `latest`

85b44736

ijjk added created-by: Next.js team

devjiwonchoi changed the title ~~[release-legacy] fix: backport release dist tag is `latest`~~ [release-legacy] fix: set `stable` dist tag for backport releases instead of `latest` 308 days ago

devjiwonchoi commented on 2025-05-24

Update console

1a2e19e6

devjiwonchoi requested a review from

ztanner 308 days ago

devjiwonchoi requested a review from

eps1lon 308 days ago

devjiwonchoi requested a review from

ijjk 308 days ago

ijjk approved these changes on 2025-05-24

devjiwonchoi marked this pull request as ready for review 308 days ago

devjiwonchoi merged 2bb5ed21 into canary 308 days ago

devjiwonchoi deleted the jiwon/05-24-_release-legacy_fix_backport_release_dist_tag_is_latest_ branch 308 days ago

github-actions added locked

github-actions locked as resolved and limited conversation to collaborators 293 days ago

Reviewers

ijjk

ztanner

eps1lon

Assignees

No one assigned

Labels

created-by: Next.js team locked

Milestone

No milestone

next.js [release-legacy] fix: set `stable` dist tag for backport releases instead of `latest` #79596 Merged

[release-legacy] fix: set `stable` dist tag for backport releases instead of `latest` #79596

next.js
[release-legacy] fix: set `stable` dist tag for backport releases instead of `latest`
#79596

Merged