Skip to content

Make older release pages durable using tags and SHAs that won't break if main changes - #10375

Draft
Alan Zimmer (alzimmermsft) wants to merge 1 commit into
mainfrom
UpdateHistoricalReleaseNotesToMatchTemplateAndShaPattern
Draft

Alan Zimmer (alzimmermsft) wants to merge 1 commit into
mainfrom
UpdateHistoricalReleaseNotesToMatchTemplateAndShaPattern

Conversation

@alzimmermsft

Copy link
Copy Markdown
Member

Found that some release pages broke after Java began removing abandoned and deprecated packages from the repository. This was due to older release pages using the main branch as the URL target rather than the release tag or the release SHA (for cases where the link is ambiguous on a given package or the release was missing things like a CHANGELOG file).

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant