Skip to content

Build(deps): bump the rstest-bdd group across 1 directory with 2 updates - #217

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/rstest-bdd-df5cd3b972
Open

Build(deps): bump the rstest-bdd group across 1 directory with 2 updates#217
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/rstest-bdd-df5cd3b972

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 3, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the rstest-bdd group with 2 updates in the / directory: rstest-bdd and rstest-bdd-macros.

Updates rstest-bdd from 0.5.0 to 0.6.0

Release notes

Sourced from rstest-bdd's releases.

Harnesses for all!

What's Changed

... (truncated)

Changelog

Sourced from rstest-bdd's changelog.

Changelog

Unreleased

  • Deprecated lookup_step, find_step, lookup_step_async, find_step_async, lookup_step_async_with_mode, find_step_async_with_mode, and find_step_with_mode in favour of lookup_step_with_metadata and find_step_with_metadata; callers should project the needed Step field. find_step_with_metadata now returns Option<ResolvedStep>.

  • Raised the nextest compile budget for the trybuild-based tests from ten to twenty minutes, and the default profile's global timeout from twenty to forty minutes so the larger per-test budget can be spent. A CI run with a cold compiler cache exceeded the old budget while healthily compiling the fixture dependency tree; the same test takes about three minutes once the cache is warm. A passing test never spends the budget.

  • Scenarios that previously passed may now correctly fail: unhinted steps that return a local alias of Result<T, E> now propagate Err rather than boxing it as a payload. Ok(T) injects T, and E must implement Display.

  • Feature paths in diagnostics and reports are now manifest-relative (ScenarioMetadata::feature_path, the JSON reporter, the JUnit classname attribute and cargo bdd --dump-steps): a feature file within the crate's manifest directory is reported as tests/features/login.feature instead of an absolute build-machine path. Files outside the manifest stay absolute. JUnit consumers key test history on classname + name; expect a one-time discontinuity, after which the value is stable everywhere. See the v0.6.0 migration guide's breaking-change section.

  • #[scenario] and scenarios! now register every bound .feature file as a Cargo rebuild dependency, so editing only a .feature file recompiles the scenario binary and the tests reflect the new text immediately (ADR-010). A feature-file path sharing no filesystem root with the manifest directory (for example a different Windows drive) is a compile error naming the file; use a manifest-relative path or a path on the same root. Adds a tested build.rs recipe closing the file-addition gap: a single cargo::rerun-if-changed directory line, carried as executed living documentation in the users' guide.

  • StepContext::insert_value now returns an InsertOutcome enum instead of Option<Box<dyn Any>>, distinguishing a recorded override (carrying any displaced previous override) from values dropped because no fixture matches the type (NoMatch) or because multiple fixtures match (AmbiguousIgnored). The previous None conflated all three cases. Use into_previous() where the old Option behaviour is needed.

  • Redesigned StepContext borrowing to be guard-based (ADR-012): borrow methods take &self, so one step can hold mutable guards for distinct fixtures concurrently — including mutable harness context plus mutable world state — without E0499/E0502. New try_borrow and try_borrow_mut methods return a typed FixtureBorrowError (NotFound, TypeMismatch, AlreadyBorrowed, NotMutable) instead of panicking on conflicting borrows; the Option-based borrow methods remain as conveniences. FixtureRef/

... (truncated)

Commits
  • 72fb226 Refresh published GPUI fixture version
  • c21c5d2 Bump version
  • 30c0a31 Generate the users-guide reference links from one base URL (#537) (#747)
  • 7f3d8c2 Prefetch fixture dependencies before the mutation lane runs (#721) (#741)
  • 6cb92fa Enforce the Python 400-line module budget on every module (#742) (#746)
  • 5a738ff Clarify Python exception documentation (#732) (#745)
  • 9ff970a Fix actionlint expression finding in lockfile refresh workflow (#709) (#735)
  • 3f62617 Chore(deps): bump ctor in / (#708)
  • 9f35338 Correct the termination term: a grace period, not a whole slow-timeout (#725)
  • 51a3c52 Bind the lockfile refresh head ref in the environment (#702)
  • Additional commits viewable in compare view

Updates rstest-bdd-macros from 0.5.0 to 0.6.0

Release notes

Sourced from rstest-bdd-macros's releases.

Harnesses for all!

What's Changed

... (truncated)

Changelog

Sourced from rstest-bdd-macros's changelog.

Changelog

Unreleased

  • Deprecated lookup_step, find_step, lookup_step_async, find_step_async, lookup_step_async_with_mode, find_step_async_with_mode, and find_step_with_mode in favour of lookup_step_with_metadata and find_step_with_metadata; callers should project the needed Step field. find_step_with_metadata now returns Option<ResolvedStep>.

  • Raised the nextest compile budget for the trybuild-based tests from ten to twenty minutes, and the default profile's global timeout from twenty to forty minutes so the larger per-test budget can be spent. A CI run with a cold compiler cache exceeded the old budget while healthily compiling the fixture dependency tree; the same test takes about three minutes once the cache is warm. A passing test never spends the budget.

  • Scenarios that previously passed may now correctly fail: unhinted steps that return a local alias of Result<T, E> now propagate Err rather than boxing it as a payload. Ok(T) injects T, and E must implement Display.

  • Feature paths in diagnostics and reports are now manifest-relative (ScenarioMetadata::feature_path, the JSON reporter, the JUnit classname attribute and cargo bdd --dump-steps): a feature file within the crate's manifest directory is reported as tests/features/login.feature instead of an absolute build-machine path. Files outside the manifest stay absolute. JUnit consumers key test history on classname + name; expect a one-time discontinuity, after which the value is stable everywhere. See the v0.6.0 migration guide's breaking-change section.

  • #[scenario] and scenarios! now register every bound .feature file as a Cargo rebuild dependency, so editing only a .feature file recompiles the scenario binary and the tests reflect the new text immediately (ADR-010). A feature-file path sharing no filesystem root with the manifest directory (for example a different Windows drive) is a compile error naming the file; use a manifest-relative path or a path on the same root. Adds a tested build.rs recipe closing the file-addition gap: a single cargo::rerun-if-changed directory line, carried as executed living documentation in the users' guide.

  • StepContext::insert_value now returns an InsertOutcome enum instead of Option<Box<dyn Any>>, distinguishing a recorded override (carrying any displaced previous override) from values dropped because no fixture matches the type (NoMatch) or because multiple fixtures match (AmbiguousIgnored). The previous None conflated all three cases. Use into_previous() where the old Option behaviour is needed.

  • Redesigned StepContext borrowing to be guard-based (ADR-012): borrow methods take &self, so one step can hold mutable guards for distinct fixtures concurrently — including mutable harness context plus mutable world state — without E0499/E0502. New try_borrow and try_borrow_mut methods return a typed FixtureBorrowError (NotFound, TypeMismatch, AlreadyBorrowed, NotMutable) instead of panicking on conflicting borrows; the Option-based borrow methods remain as conveniences. FixtureRef/

... (truncated)

Commits
  • 72fb226 Refresh published GPUI fixture version
  • c21c5d2 Bump version
  • 30c0a31 Generate the users-guide reference links from one base URL (#537) (#747)
  • 7f3d8c2 Prefetch fixture dependencies before the mutation lane runs (#721) (#741)
  • 6cb92fa Enforce the Python 400-line module budget on every module (#742) (#746)
  • 5a738ff Clarify Python exception documentation (#732) (#745)
  • 9ff970a Fix actionlint expression finding in lockfile refresh workflow (#709) (#735)
  • 3f62617 Chore(deps): bump ctor in / (#708)
  • 9f35338 Correct the termination term: a grace period, not a whole slow-timeout (#725)
  • 51a3c52 Bind the lockfile refresh head ref in the environment (#702)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added cargo Dependabot channel for Rust crate updates. dependencies Dependency updates, applied to every Dependabot pull request. labels Oct 3, 2026
@github-actions
github-actions Bot enabled auto-merge (squash) October 3, 2026 15:39
@coderabbitai

coderabbitai Bot commented Oct 3, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

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

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: eb0f82d9-84cf-40c4-b11c-1c62702e899c

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

Use the checkbox below for a quick retry:

  • Trigger review

codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from d2cad1e to 805d58b Compare October 9, 2026 17:28
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 805d58b to f793d12 Compare October 11, 2026 10:01
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from f793d12 to 6f42c06 Compare October 12, 2026 13:33
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 6f42c06 to b9f95bc Compare October 15, 2026 04:14
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from b9f95bc to a5e9b7b Compare October 18, 2026 06:24
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from a5e9b7b to 1b4bb0d Compare October 28, 2026 05:04
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 1b4bb0d to 4755dc7 Compare October 28, 2026 05:30
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 4755dc7 to b7ec9bc Compare November 2, 2026 04:33
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from b7ec9bc to 7e7abfa Compare November 3, 2026 04:14
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 7e7abfa to 40512ac Compare November 9, 2026 04:28
@sourcery-ai

sourcery-ai Bot commented Nov 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Reviewer's Guide

Configuration

Bump the direct rstest-bdd and rstest-bdd-macros dependency declarations to 0.6.0 together, keeping the paired crates on the same release.

  • Cargo.toml L72-74

Lock files and vendored code

Review the regenerated lockfile entries corresponding to the dependency upgrades.

  • Cargo.lock L534-554, L2259-2270, L3442-3481 (+36 small edits)
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 40512ac to 7e98667 Compare November 10, 2026 04:14
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 7e98667 to 5f59ac1 Compare November 11, 2026 04:37
codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@dependabot
Build(deps): bump the rstest-bdd group across 1 directory with 2 updates
905a614 
Bumps the rstest-bdd group with 2 updates in the / directory: [rstest-bdd](https://github.com/leynos/rstest-bdd) and [rstest-bdd-macros](https://github.com/leynos/rstest-bdd).


Updates `rstest-bdd` from 0.5.0 to 0.6.0
- [Release notes](https://github.com/leynos/rstest-bdd/releases)
- [Changelog](https://github.com/leynos/rstest-bdd/blob/main/docs/CHANGELOG.md)
- [Commits](leynos/rstest-bdd@v0.5.0...v0.6.0)

Updates `rstest-bdd-macros` from 0.5.0 to 0.6.0
- [Release notes](https://github.com/leynos/rstest-bdd/releases)
- [Changelog](https://github.com/leynos/rstest-bdd/blob/main/docs/CHANGELOG.md)
- [Commits](leynos/rstest-bdd@v0.5.0...v0.6.0)

---
updated-dependencies:
- dependency-name: rstest-bdd
  dependency-version: 0.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rstest-bdd
- dependency-name: rstest-bdd-macros
  dependency-version: 0.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rstest-bdd
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/rstest-bdd-df5cd3b972 branch from 5f59ac1 to 905a614 Compare November 12, 2026 04:14

This branch has not been deployed

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

Reviewers

1 more reviewer
@codescene-access codescene-access[bot] codescene-access[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

cargo Dependabot channel for Rust crate updates. dependencies Dependency updates, applied to every Dependabot pull request.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants