BUG: usage links using wrong release in base URL #584
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the base URL that is being used to generate the artifact links in the MP usage tutorial was never updated in the 2022.2 release (PR xref here). the way i've dev bumped subsequent releases has just been a find/replace for n-1 release -> current release, so this got missed for two years. this surfaced because of this forum post from Luca, pointing out that the ancombc links don't work (which makes sense b/c that functionality didn't exist in 2021.11). in any case- this shouldn't come up again with my current process, but i'd like to find a way to add some sort of URL validation so that things don't get left behind like this in the future.