We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Pester (latest)
All
⚠️ Pending PR pester/docs#316
Should we do a patch release for v5 to update https://pester.dev/docs/* links to https://pester.dev/docs/v5/* ? Once Pester v6 stable version is released, https://pester.dev/docs/* URIs will likely point to v6-docs which will cause dead links and wrong content for v5-users.
If done, should we consider a v4 patch release as a quality of life fix as well?
The text was updated successfully, but these errors were encountered:
v5 yes v4 probably no, because it would change the certificate for very little benefit, and we said we will patch only critical issues.
Sorry, something went wrong.
Good point. Forgot that v4 is signed
No branches or pull requests
Checklist
Where did you see it?
Pester (latest)
Function name
All
What is the issue?
Should we do a patch release for v5 to update https://pester.dev/docs/* links to https://pester.dev/docs/v5/* ? Once Pester v6 stable version is released, https://pester.dev/docs/* URIs will likely point to v6-docs which will cause dead links and wrong content for v5-users.
If done, should we consider a v4 patch release as a quality of life fix as well?
The text was updated successfully, but these errors were encountered: