Skip to content

chore(deps): upgrade dependencies#62

Open
libreworksautomation[bot] wants to merge 1 commit intomainfrom
github-actions/upgrade-main
Open

chore(deps): upgrade dependencies#62
libreworksautomation[bot] wants to merge 1 commit intomainfrom
github-actions/upgrade-main

Conversation

@libreworksautomation
Copy link
Contributor

@libreworksautomation libreworksautomation bot commented Feb 16, 2026 •
edited
Loading

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

github-actions[bot]
github-actions bot previously approved these changes Feb 16, 2026
View reviewed changes
@codecov
Copy link

codecov bot commented Feb 16, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (798edda) to head (ddaaa85).

Additional details and impacted files 
@@            Coverage Diff            @@
##              main       #62   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines          701       701           
  Branches        89        89           
=========================================
  Hits           701       701

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mergify mergify bot added the queued label Feb 16, 2026
@mergify
Copy link

mergify bot commented Feb 16, 2026 •
edited
Loading

Merge Queue Status

Rule: default

  • ✅ Entered queue — 2026-02-16 02:03 UTC
  • ✅ Checks started · in-place
  • 🚫 Left the queue — 2026-02-16 02:03 UTC · at e201f78715550d572cc3936c9b929f5dcd39e76e

This pull request spent 8 seconds in the queue, with no time running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate PR title
    • check-neutral = Validate PR title
    • check-skipped = Validate PR title
  • any of [🛡 GitHub branch protection]:
    • check-success = approve
    • check-neutral = approve
    • check-skipped = approve
  • any of [🛡 GitHub branch protection]:
    • check-success = build
    • check-neutral = build
    • check-skipped = build
  • any of [🛡 GitHub branch protection]:
    • check-skipped = self-mutation
    • check-neutral = self-mutation
    • check-success = self-mutation

Reason

Pull request #62 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 2 of 4 required status checks are queued.)

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify bot added dequeued and removed queued labels Feb 16, 2026
@libreworksautomation libreworksautomation bot force-pushed the github-actions/upgrade-main branch from e201f78 to 45a154a Compare February 23, 2026 02:02
github-actions[bot]
github-actions bot previously approved these changes Feb 23, 2026
View reviewed changes
@mergify mergify bot added queued and removed dequeued labels Feb 23, 2026
@mergify
Copy link

mergify bot commented Feb 23, 2026

Merge Queue Status

Rule: default

  • ✅ Entered queue — 2026-02-23 02:05 UTC
  • ✅ Checks started · in-place
  • 🚫 Left the queue — 2026-02-23 02:05 UTC · at 45a154afa29e6eff35c23471b13992af029e518f

This pull request spent 5 seconds in the queue, with no time running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate PR title
    • check-neutral = Validate PR title
    • check-skipped = Validate PR title
  • any of [🛡 GitHub branch protection]:
    • check-success = approve
    • check-neutral = approve
    • check-skipped = approve
  • any of [🛡 GitHub branch protection]:
    • check-success = build
    • check-neutral = build
    • check-skipped = build
  • any of [🛡 GitHub branch protection]:
    • check-skipped = self-mutation
    • check-neutral = self-mutation
    • check-success = self-mutation

Reason

Pull request #62 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 2 of 4 required status checks have not succeeded: 1 expected.)

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify bot added dequeued and removed queued labels Feb 23, 2026
@github-actions
chore(deps): upgrade dependencies
ddaaa85 
Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/libreworks/db-provision-pgsql/actions/runs/22558317749

------

*Automatically created by projen via the "upgrade-main" workflow*

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@libreworksautomation libreworksautomation bot force-pushed the github-actions/upgrade-main branch from 45a154a to ddaaa85 Compare March 2, 2026 01:59
@mergify mergify bot added queued and removed dequeued labels Mar 2, 2026
@mergify
Copy link

mergify bot commented Mar 2, 2026

Merge Queue Status

Rule: default

  • ✅ Entered queue — 2026-03-02 02:01 UTC
  • ✅ Checks started · in-place
  • 🚫 Left the queue — 2026-03-02 02:01 UTC · at ddaaa85cc0793893b7e40c0c7eb59999f948ff3e

This pull request spent 17 seconds in the queue, with no time running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate PR title
    • check-neutral = Validate PR title
    • check-skipped = Validate PR title
  • any of [🛡 GitHub branch protection]:
    • check-success = approve
    • check-neutral = approve
    • check-skipped = approve
  • any of [🛡 GitHub branch protection]:
    • check-success = build
    • check-neutral = build
    • check-skipped = build
  • any of [🛡 GitHub branch protection]:
    • check-skipped = self-mutation
    • check-neutral = self-mutation
    • check-success = self-mutation

Reason

Pull request #62 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: 2 of 4 required status checks are in progress.)

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify bot added dequeued and removed queued labels Mar 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

auto-approve dequeued

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants