Skip to content

chore(deps): update dependency @doist/prettier-config to v4#258

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/doist-prettier-config-4.x
Open

chore(deps): update dependency @doist/prettier-config to v4#258
renovate[bot] wants to merge 1 commit intomainfrom
renovate/doist-prettier-config-4.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 5, 2025

This PR contains the following updates:

Package Change Age Confidence
@doist/prettier-config 3.0.54.0.1 age confidence

Release Notes

Doist/prettier-config (@​doist/prettier-config)

v4.0.1

Compare Source

v4.0.0

Compare Source

  • Updated prettier to ^3.0.0 #​21

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Monday through Friday (* * * * 1-5)
  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Nov 5, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: todoist-google-sheets@1.0.0
npm error Found: prettier@2.8.8
npm error node_modules/prettier
npm error   dev prettier@"2.8.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer prettier@"^3.0.0" from @doist/prettier-config@4.0.1
npm error node_modules/@doist/prettier-config
npm error   dev @doist/prettier-config@"4.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-29T17_58_41_122Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-29T17_58_41_122Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/doist-prettier-config-4.x branch from 32f2e3c to a6d127c Compare November 18, 2025 23:41
@renovate renovate Bot force-pushed the renovate/doist-prettier-config-4.x branch from a6d127c to f9271f2 Compare December 3, 2025 15:41
@renovate renovate Bot force-pushed the renovate/doist-prettier-config-4.x branch from f9271f2 to e8807be Compare December 31, 2025 18:06
@renovate renovate Bot force-pushed the renovate/doist-prettier-config-4.x branch from e8807be to 70866b2 Compare January 23, 2026 21:10
@renovate renovate Bot force-pushed the renovate/doist-prettier-config-4.x branch 2 times, most recently from 8b34ceb to e57f5e3 Compare February 17, 2026 18:12
@renovate renovate Bot force-pushed the renovate/doist-prettier-config-4.x branch from e57f5e3 to 72a2919 Compare March 5, 2026 16:18
@renovate renovate Bot force-pushed the renovate/doist-prettier-config-4.x branch from 72a2919 to 5758441 Compare April 29, 2026 17:58
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.

0 participants