Skip to content

bluebird@3.0.5 breaks build ⚠️#102

Closed
greenkeeperio-bot wants to merge 1 commit into
masterfrom
greenkeeper-bluebird-3.0.5
Closed

bluebird@3.0.5 breaks build ⚠️#102
greenkeeperio-bot wants to merge 1 commit into
masterfrom
greenkeeper-bluebird-3.0.5

Conversation

@greenkeeperio-bot

Copy link
Copy Markdown
Contributor

Hello 👋

⚠️⚠️⚠️

bluebird just published its new version 3.0.5, which is covered by your current version range. After updating it in your project the build kept failing.

This means it’s possible that your software is malfunctioning, because of this update. Use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


GitHub Release

Bugfixes:


This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

@codecov-io

Copy link
Copy Markdown

Current coverage is 94.73%

Merging #102 into master will not affect coverage as of a925656

@@            master    #102   diff @@
======================================
  Files            1       1       
  Stmts          361     361       
  Branches         0       0       
  Methods          0       0       
======================================
  Hit            342     342       
  Partial          0       0       
  Missed          19      19       

Review entire Coverage Diff as of a925656


Uncovered Suggestions

  1. +0.83% via lib/urllib.js#490...492
  2. +0.56% via lib/urllib.js#742...743
  3. +0.56% via lib/urllib.js#731...732
  4. See 7 more...

Powered by Codecov. Updated on successful CI builds.

@fengmk2 fengmk2 closed this Dec 9, 2015
@fengmk2 fengmk2 deleted the greenkeeper-bluebird-3.0.5 branch December 9, 2015 06:07
fengmk2 added a commit that referenced this pull request Jul 1, 2026
Update `voidzero-dev/setup-vp` from the floating `@v1` tag to the pinned
latest commit on `main`
([13e7afb](voidzero-dev/setup-vp@13e7afb),
feat: resolve Vite+ version from package.json / catalog / lockfile
#102).

This matches the repo convention of SHA-pinning actions with a version
comment. Applied across `nodejs.yml`, `release.yml`, and
`pkg.pr.new.yml` (4 references).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated automated workflows to use a fixed version of a third-party
setup action for more consistent and reliable runs.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants