Skip to content

Add documentation for include_assets build step with manifest generation#7017

Closed
alfonso-noriega wants to merge 1 commit intoadd_manifest_to_include_files_stepfrom
docs_manifest_generation_include_assets_step
Closed

Add documentation for include_assets build step with manifest generation#7017
alfonso-noriega wants to merge 1 commit intoadd_manifest_to_include_files_stepfrom
docs_manifest_generation_include_assets_step

Conversation

@alfonso-noriega
Copy link
Contributor

WHY are these changes introduced?

Fixes #0000

WHAT is this pull request doing?

How to test your changes?

Post-release steps

Measuring impact

How do we know this change was effective? Please choose one:

  • n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
  • Existing analytics will cater for this addition
  • PR includes analytics changes to measure impact

Checklist

  • I've considered possible cross-platform impacts (Mac, Linux, Windows)
  • I've considered possible documentation changes

Covers all inclusion types (pattern, static, configKey), the new
generateManifest flag, anchor/groupBy fields for grouped manifest
entries, path resolution behaviour, rename-on-conflict semantics,
and a full end-to-end TOML example.
@alfonso-noriega alfonso-noriega requested a review from a team as a code owner March 16, 2026 14:33
@github-actions
Copy link
Contributor

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

Copy link
Contributor Author

alfonso-noriega commented Mar 16, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant