Add release 1.29 to previousPatches in the schedule.yaml #44344
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
/cc @sftim @reylejano This may require attention, particularly due to its wider impact including the Install Tools pages. With the new release, these pages will attract additional attention, as people may be interested in trying out the new release. |
|
We should also fix the shortcode to work when there's no previous release listed. Would you like to file an issue about making that fix @dipesh-rawat ? There is a fallback in the shortcode but I think it is buggy. |
|
Thanks /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. Git tree hash: 17cf65b1a01e4e497b95cfbda86eace4c3bcfab2
|
Resolves #44330
Additional Context:
Despite being reported for a single page, this is a broader site-wide issue affecting multiple pages using
{{< skew currentPatchVersion >}}.The shortcode "
{{< skew currentPatchVersion >}}" seems to be struggling to determine the latest patch version with new 1.29 release. The current output from shortcode is%!f(string=1.).0.(see here). The quick fix involves updating the schedule.yaml to incorporate the latest version, v1.29.0, ensuring the shortcode displays the expected value.Fixed Preview Page | Current Broken Website Page