Which version should I use?
The big picture: Blueprint is under active development, and work lands on main
every day. The 0.8 changes ship in 0.8 and are large; 0.9 is planned to be their first
end-to-end validation. The Tags and Releases pages on GitLab show what has been tagged.
Why it matters: This docs site describes main, not a tag. If you clone v0.7.0 and
follow these pages, you follow instructions for a different version. Pick a path first.
What changed in 0.8
Section titled “What changed in 0.8”0.8 ships roughly 140 changelog fragments since v0.7.0, including security fixes. The highlights:
- One-command setup.
scripts/customize.sh --initreplaces the oldrm -rf .gitstep and records.blueprint-version. /kickoffbootstraps the GitLab project (merge-request settings, protected branches and tags, labels) throughscripts/gitlab-bootstrap.sh./specruns a spec’s whole lifecycle underdocs/specs/, backed by a stricter spec completeness gate./waveruns several issues in parallel (renamed frombatch), with a pre-flight that checks each issue before a worktree is created.make statusand/nextshow which lifecycle step you are on and the one command to type next.- A rigor floor (
.claude/rigor.json) lists the paths that always get the heavier audit. - CI supply-chain gates: images pinned by digest, optional SAST and secret-detection severity gates, and image signing with SBOM attestations.
- Security fixes to the
security::deferredcheck,scripts/gitlab-bootstrap.sh, and the bash deny hook.
The full list is the changelog.d/ directory in the repository.
Option 1: use 0.7 (v0.7.0)
Section titled “Option 1: use 0.7 (v0.7.0)”Choose this if you want a tagged release and can live without what came after it.
git clone --branch v0.7.0 --depth 1 https://gitlab.com/macrodream/blueprint.git my-projectThen follow the docs that ship in the tag, not this site: open
website/src/content/docs/getting-started/start-a-project.md in your clone, or browse
the v0.7.0 docs tree.
The v0.7.0 release notes
describe what that tag contains.
Caveats:
- There is no automated upgrade path from 0.7 to 0.8. Upgrading from 0.7 lists the manual changes.
- It does not have the fixes made since, including the security entries.
- Its setup step differs: it uses
rm -rf .gitandgit init, and has no.blueprint-version.
Option 2: use 0.8 (main)
Section titled “Option 2: use 0.8 (main)”Choose this if you want the current workflow and can tolerate churn. Follow this docs site.
Until 0.8 is tagged, main is the only place it exists; once it ships in 0.8, the Tags
page lists the tag.
Clone the default branch. scripts/customize.sh --init refuses a detached HEAD, so do not
clone a tag or a bare commit for this path.
Caveats:
mainstill moves daily. What you clone today may differ from what you clone next week.- 0.8 has been checked mostly at the gate and self-test level, not end to end on a real project. Expect rough edges.
- Record where you started.
--initwrites the commit to.blueprint-version. - Report problems through the giving feedback guide.
Option 3: wait for 0.9
Section titled “Option 3: wait for 0.9”Choose this if you would rather start from a release that someone has used the whole way
through. 0.9 is planned to be validated by a full intake of a real project: /kickoff,
then a spec, then a first milestone, then a release, end to end. This page will be
updated when that happens. No dates are promised.
Caveat: waiting gets you a more proven path but not a faster one, and any 0.9 plan can still change.