-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
Storybook and Tailwind configuration previews: Updating |
It looks like the self-hosted version still isn't using the pnpm configuration script and TS version is being knocked back down 😢 |
Can we do the pnpm/ node updates manually, but keep renovate for other dependencies? |
We could, but I'd really prefer if we figured out how to make Renovate work properly with the pnpm script. Even if we have to truly self-host it on an AWS instance or something it seems worth getting it working. Or we could use dependabot for pnpm dependencies for now and Renovate for the rest until we figure it out. That seems like probably the least uplift option that gets us into a manageable state for the time being without distracting us from some other higher value things than tinkering with Renovate. |
Made an issue for us to do just that: WordPress/openverse#544 |
1 similar comment
Made an issue for us to do just that: WordPress/openverse#544 |
42efc60
to
dcc2a27
Compare
dcc2a27
to
15232c8
Compare
Closing as this will not be addressed at the moment. |
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will now ignore this update (7.2.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
This PR contains the following updates:
7.1.0
->7.2.1
Release Notes
pnpm/pnpm
v7.2.1
Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.2.0...v7.2.1
v7.2.0
Compare Source
Minor Changes
A new setting is supported for ignoring specific deprecation messages:
pnpm.allowedDeprecatedVersions
. The setting should be provided in thepnpm
section of the rootpackage.json
file. The below example will mute any deprecation warnings about therequest
package and warnings aboutexpress
v1:Related issue: #4306
Related PR: #4864
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.9...v7.2.0
v7.1.9
Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.8...v7.1.9
v7.1.8
Compare Source
Patch Changes
package.json
file #4822.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.7...v7.1.8
v7.1.7
Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.6...v7.1.7
v7.1.6
Compare Source
Patch Changes
auto-install-peers
is set totrue
#4796.NODE_ENV=production pnpm install --dev
should only install dev deps #4745.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.5...v7.1.6
v7.1.5
Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.4...v7.1.5
v7.1.4
Compare Source
Patch Changes
Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.3...v7.1.4
v7.1.3
Compare Source
Patch Changes
auto-install-peers
is set totrue
, automatically install missing peer dependencies without writing them topackage.json
as dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #4776.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.2...v7.1.3
v7.1.2
Compare Source
Patch Changes
pnpm setup
should not fail on Windows ifPNPM_HOME
is not yet in the system registry #4757pnpm dlx
shouldn't modify the lockfile in the current working directory #4743.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.1...v7.1.2
v7.1.1
Compare Source
Patch Changes
node_modules/.pnpm
and inside the global store #4716pnpm create <pkg>
should be passed to the executed create app package. Sopnpm create next-app --typescript
should work`.Our Sponsors
Full Changelog: pnpm/pnpm@v7.1.0...v7.1.1
Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.