Skip to content

Bump build_test from 2.2.3 to 3.2.1 #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 1, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 30, 2025

Bumps build_test from 2.2.3 to 3.2.1.

Release notes

Sourced from build_test's releases.

package:build_test v3.2.1

  • Files loaded from disk for resolveSources and testBuilders that are in the same package as explicitly-passed test inputs are now loaded if they match the default globs, such as lib/**, instead of ignored. This more closely matches version 2 behavior.

package:build_test v3.2.0

  • Fixes when passing a readerWriter to testBuilders: don't count initial assets as outputs; do set up packages for initial assets; only apply builders to packages mentioned in sourceAssets.
  • Add readAllSourcesFromFilesystem parameter to resolveSources. Set it to true to make the method behave as it did in build_test 2.2.0.
  • Fix to resolveSources error handling.

package:build_test v3.1.1

  • Bug fix: stop parsing testBuilder asset paths as globs.

package:build_test v3.1.0

  • Add inputsTrackedFor and resolverEntrypointsTrackedFor to ReaderWriterTesting, so tests can determine what each build step read and resolved.
  • Add loadIsolateSources to ReaderWriterTesting. It loads all real sources visible to the test into memory.
  • testBuilder default onLog now works outside of tests: it falls back to print instead of crashing.
  • Update README.md.

package:build_test v3.0.0

Breaking changes:

  • Breaking change: removed tearDown parameter to resolveSources for keeping resolvers across multiple tests.
  • Breaking change: tests must use new TestReaderWriter instead of InMemoryAssetReader and InMemoryAssetWriter.
  • Breaking change: testBuilder no longer accepts a reader and a writer. Instead it returns a TestBuilderResult with the TestReaderWriter that was used.
  • Breaking change: resolveSources no longer automatically reads non-input files from the filesystem; specify explicitly which non-input files the test should read in nonInputsToReadFromFilesystem.
  • Breaking change: remove MultiAssetReader. Load the source into one TestReaderWriter instead.
  • Breaking change: TestReaderWriter.assetsRead does not take into account details of the build, it's just what was actually read. Use TestReaderWriter.inputsTracked for what was recorded as an input. Note that resolver entrypoints are now tracked separately from inputs, see TestReaderWriter.resolverEntrypointsTracked.
  • Breaking change: Remove StubAssetReader. Use TestReaderWriter instead.

Other user-visible changes:

  • resolveSources and testBuilder now do a full build_runner build, with

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [build_test](https://github.com/dart-lang/build) from 2.2.3 to 3.2.1.
- [Release notes](https://github.com/dart-lang/build/releases)
- [Commits](dart-lang/build@build_test-v2.2.3...build_test-v3.2.1)

---
updated-dependencies:
- dependency-name: build_test
  dependency-version: 3.2.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dart Pull requests that update dart code dependencies Pull requests that update a dependency file labels Jun 30, 2025
Copy link

coderabbitai bot commented Jun 30, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@rrousselGit rrousselGit merged commit 7846486 into master Jul 1, 2025
1 of 2 checks passed
@dependabot dependabot bot deleted the dependabot/pub/build_test-3.2.1 branch July 1, 2025 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dart Pull requests that update dart code dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant