Skip to content

chore(deps): upgrade dependencies#59

Merged
mergify[bot] merged 2 commits intomainfrom
github-actions/upgrade-main
Jan 26, 2026
Merged

chore(deps): upgrade dependencies#59
mergify[bot] merged 2 commits intomainfrom
github-actions/upgrade-main

Conversation

@libreworksautomation
Copy link
Contributor

@libreworksautomation libreworksautomation bot commented Dec 29, 2025 •
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 Dec 29, 2025
View reviewed changes
@codecov
Copy link

codecov bot commented Dec 29, 2025 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (0af91e6) to head (a593aa1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files 
@@            Coverage Diff            @@
##              main       #59   +/-   ##
=========================================
  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 Dec 29, 2025
@mergify
Copy link

mergify bot commented Dec 29, 2025

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at be62c2e

This pull request spent 5 seconds in the queue, with no time running CI.
The checks were run in-place.

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 #59 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 requeue comment.

@mergify mergify bot added dequeued and removed queued labels Dec 29, 2025
@libreworksautomation libreworksautomation bot force-pushed the github-actions/upgrade-main branch from be62c2e to 8a9051d Compare January 5, 2026 01:47
github-actions[bot]
github-actions bot previously approved these changes Jan 5, 2026
View reviewed changes
@mergify mergify bot added queued and removed dequeued labels Jan 5, 2026
@mergify
Copy link

mergify bot commented Jan 5, 2026

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 8a9051d

This pull request spent 14 seconds in the queue, with no time running CI.
The checks were run in-place.

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 #59 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 requeue comment.

@mergify mergify bot added dequeued and removed queued labels Jan 5, 2026
@libreworksautomation libreworksautomation bot force-pushed the github-actions/upgrade-main branch from 8a9051d to 9c071a3 Compare January 12, 2026 01:44
github-actions[bot]
github-actions bot previously approved these changes Jan 12, 2026
View reviewed changes
@mergify mergify bot removed the dequeued label Jan 12, 2026
github-actions[bot]
github-actions bot previously approved these changes Jan 12, 2026
View reviewed changes
@mergify mergify bot added the queued label Jan 12, 2026
@mergify
Copy link

mergify bot commented Jan 12, 2026

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 6d3eec3

This pull request spent 5 seconds in the queue, with no time running CI.
The checks were run in-place.

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 #59 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 requeue comment.

@mergify mergify bot added dequeued and removed queued labels Jan 12, 2026
@libreworksautomation libreworksautomation bot force-pushed the github-actions/upgrade-main branch from 6d3eec3 to 71017d5 Compare January 19, 2026 01:45
github-actions[bot]
github-actions bot previously approved these changes Jan 19, 2026
View reviewed changes
@mergify mergify bot removed the dequeued label Jan 19, 2026
github-actions[bot]
github-actions bot previously approved these changes Jan 19, 2026
View reviewed changes
@mergify mergify bot added the queued label Jan 19, 2026
@mergify
Copy link

mergify bot commented Jan 19, 2026

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 7b76f44

This pull request spent 5 seconds in the queue, with no time running CI.
The checks were run in-place.

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 #59 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 requeue comment.

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

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

------

*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 7b76f44 to 2d7d0f1 Compare January 26, 2026 01:48
github-actions[bot]
github-actions bot previously approved these changes Jan 26, 2026
View reviewed changes
@mergify mergify bot removed the dequeued label Jan 26, 2026
@github-actions
chore: self mutation
a593aa1 
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@mergify mergify bot added the queued label Jan 26, 2026
@mergify mergify bot merged commit 358e372 into main Jan 26, 2026
9 checks passed
@mergify
Copy link

mergify bot commented Jan 26, 2026

Merge Queue Status

✅ The pull request has been merged at a593aa1

This pull request spent 5 seconds in the queue, with no time running CI.
The checks were run in-place.

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

@mergify mergify bot deleted the github-actions/upgrade-main branch January 26, 2026 01:51
@mergify mergify bot removed the queued label Jan 26, 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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants