Skip to content
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

Update shapeless to 2.3.11 #669

Merged
merged 1 commit into from
May 16, 2024

Update shapeless to 2.3.11

bf20879
Select commit
Loading
Failed to load commit list.
Merged

Update shapeless to 2.3.11 #669

Update shapeless to 2.3.11
bf20879
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded May 16, 2024 in 0s

2 potential rules

Rule: merge scala-steward's PRs (merge)

  • -closed [πŸ“Œ merge requirement]
  • -conflict [πŸ“Œ merge requirement]
  • -draft [πŸ“Œ merge requirement]
  • author=typelevel-steward[bot]
  • status-success=Build and Test (ubuntu-latest, 2.12, temurin@8, rootJS)
  • status-success=Build and Test (ubuntu-latest, 2.12, temurin@8, rootJVM)
  • status-success=Build and Test (ubuntu-latest, 2.12, temurin@8, rootNative)
  • status-success=Build and Test (ubuntu-latest, 2.13, temurin@8, rootJS)
  • status-success=Build and Test (ubuntu-latest, 2.13, temurin@8, rootJVM)
  • status-success=Build and Test (ubuntu-latest, 2.13, temurin@8, rootNative)
  • status-success=Build and Test (ubuntu-latest, 3, temurin@8, rootJS)
  • status-success=Build and Test (ubuntu-latest, 3, temurin@8, rootJVM)
  • status-success=Build and Test (ubuntu-latest, 3, temurin@8, rootNative)
  • any of:
    • body~=labels:.*early-semver-patch
    • body~=labels:.*early-semver-minor
  • any of: [πŸ“Œ merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed

Rule: Label core PRs (label)

  • files~=^core/

πŸ’–Β Β Mergify is proud to provide this service for free to open source projects.

πŸš€Β Β You can help us by becoming a sponsor!


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com