Skip to content

Commit

Permalink
fix(docs): Force docs build using latest released code always (#3762)
Browse files Browse the repository at this point in the history
Having two different docs builds, one with released code and one
without, doesn't fly with build-system, since it checks the content hash
of the content to determine whether to rebuild based on committed data
only. This means that the hack introduced
[here](#3716) does
not work.

So we'll just build as if we were in master on every run, for now.
  • Loading branch information
spalladino committed Dec 21, 2023
1 parent f3d93aa commit 5545ee6
Showing 1 changed file with 6 additions and 8 deletions.
14 changes: 6 additions & 8 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -853,15 +853,13 @@ jobs:
name: "Copy docs dockerignore"
command: cp docs/.dockerignore .
- run:
name: "Configure build for master"
name: "Require released code"
command: |
if [ "$CIRCLE_BRANCH" == "master" ]; then
echo Configuring build for master
echo "INCLUDE_RELEASED_CODE=1" >> docs/.env
LAST_TAG="aztec-packages-v$(jq -r '.["."]' .release-please-manifest.json)"
echo Fetching latest released tag $LAST_TAG
git fetch origin --refetch --no-filter refs/tags/$LAST_TAG:refs/tags/$LAST_TAG
fi
echo Requiring released code snippets
echo "INCLUDE_RELEASED_CODE=1" >> docs/.env
LAST_TAG="aztec-packages-v$(jq -r '.["."]' .release-please-manifest.json)"
echo Fetching latest released tag $LAST_TAG
git fetch origin --refetch --no-filter refs/tags/$LAST_TAG:refs/tags/$LAST_TAG
- run:
name: "Build docs"
command: build docs
Expand Down

0 comments on commit 5545ee6

Please sign in to comment.