website: Use latest release rather than edge #7781
Merged
+39
−3
Conversation
This file contains hidden or 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
srenatus
reviewed
Jul 17, 2025
charlieegan3
force-pushed
the
netlify-latest-release
branch
6 times, most recently
from
c42c4ad to
1e76158
Compare
✅ Deploy Preview for openpolicyagent ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
charlieegan3
force-pushed
the
netlify-latest-release
branch
6 times, most recently
from
620b9b5 to
766c8a3
Compare
docs/Makefile
Outdated
| git diff-index --quiet HEAD -- || (echo "Latest release build must be done without working changes" && exit 1) | ||
| git fetch --tags origin | ||
| $(eval CURRENT_BRANCH := $(shell git branch --show-current)) | ||
| git checkout $$(git describe --tags --abbrev=0) |
There was a problem hiding this comment.
Should we assert the tag format here. I.e. that it fits the v<semver> structure we use for release tags?
There was a problem hiding this comment.
Yeah that makes sense. I have created a new tag locally to check:
$ git tag --sort=-version:refname | head -n 3
v2.15.0-fffff
v1.6.0
v1.5.1
$ git tag --sort=-version:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -1
v1.6.0
charlieegan3
force-pushed
the
netlify-latest-release
branch
6 times, most recently
from
53482ee to
f39d2ac
Compare
|
💭 Does this mean we'll stop building the website on code pushes to main, but only build it on tag pushes, if the tag also is the latest one? |
charlieegan3
force-pushed
the
netlify-latest-release
branch
from
f39d2ac to
a952ed4
Compare
|
The site will still be built on pushed to main, but only the latest tag will be used. This is because it's 'easier' and more robust than sending events at the correct time to build the site. In theory. |
charlieegan3
force-pushed
the
netlify-latest-release
branch
3 times, most recently
from
e349088 to
bc9c208
Compare
charlieegan3
force-pushed
the
netlify-latest-release
branch
from
bc9c208 to
8f724be
Compare
Merged
Signed-off-by: Charlie Egan <[email protected]>
charlieegan3
force-pushed
the
netlify-latest-release
branch
from
8f724be to
2a3ba46
Compare
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.
This is intended to make the default view of the OPA site and docs from the latest release, rather than from edge.
Deploy preview command will need to show edge, but using that to test the prod command atm.
When
make netlify-latestwas used on the preview, we see that the site was built from the latest release: