Repository navigation
chore(docs): upgrade to Blume 2 and load related packages from the hub - #63
Merged
Merged
Conversation
- Bump blume 1.6.4 to ^2.2.3 via `blume upgrade` and translate the config
to Blume 2 adapters: filesystem() and custom() from blume/sources,
analytics: [vercel()], deployment: { site }, ai.llmsTxt to agents.llmsTxt.
- Keep the custom GitHub Releases changelog source, since the built-in
githubReleases() has no way to keep release pages out of search. Wrap
withContext so Blume 2's per-scan rebuild keeps the search exclusion, and
pass the site URL so self-links become root-relative like the built-in.
- Bump @thebuilder/umbraco-docs to ^1.1.0 and allow it past the minimum
release age.
- Update the transitive zod so astro and blume share one copy, which
`blume check` needs to type-check the content collections.
Use loadUmbracoPackages() from @thebuilder/umbraco-docs 1.2.0 for the "More from TheBuilder" section, so it lists every package published at umbraco.thebuilder.dk without a hand-written copy here. Keep only this package's own manifest and drop the copied logos. Exclude @thebuilder/* from pnpm's minimum release age check, so new releases of our own packages install right away.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Summary
npx blume@latest upgradeprinted; it now reports "Ready for Blume 2.2.3".loadUmbracoPackages()from@thebuilder/umbraco-docs1.2.0, which readshttps://umbraco.thebuilder.dk/packages.jsonat build time.umbraco-package.tskeeps only this package's own manifest, and the copied logos inapps/docs/public/ecosystem/are gone. If the hub can't be reached, the build logs a warning and hides the section instead of failing.pnpm-workspace.yamlexcludes@thebuilder/*from the minimum release age check, so new releases of our own packages install right away.Notes
withContext, which would have silently dropped that exclusion, so the wrapper now re-applies it. The source now also gets the site URL, so links in release notes that point back to the docs become root-relative.blume check. Only zod was updated (pnpm --filter @thebuilder/web-analytics-docs update zod --depth Infinity). Please don't runpnpm dedupehere without checking first: it also moves the backoffice client's Vite from 8.2.2 to 8.3.4. The client still resolves Vite 8.2.2.2.2.3, like this repo's other dependencies. The client'sdompurifyandyamlmoved up a patch version, andpnpm client:testpasses 258 of 258.[email protected]release-age exception is left as it was.Testing
blume doctor,blume check(0 errors), the docs build andcheck:ogpass.og:image, and five related-package cards linking to the other packages, with logos served from umbraco.thebuilder.dk.pnpm install --frozen-lockfilepasses. A plainpnpm installleavespnpm-workspace.yamlunchanged.