cassels/dotpref

Manage CLI application encrypted preferences in a stateful way.

dotpref's Issues

The last version 2.0.3 doesn't include any code

I installed [email protected] and it just has a package.json no code in it.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Warning

These dependencies are deprecated:

Datasource	Name	Replacement PR?
npm	@types/onetime
npm	@types/pkg-up
npm	mem
npm	pkg-up

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps-dev): update dependency semantic-release to v19 [security]
• chore(deps-dev): update dependency @types/node to ^16.18.101
• chore(deps-dev): update dependency typescript to ^4.9.5
• chore(deps-dev): update linters (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-prettier, prettier)
• chore(deps): update dependency mem to v10
• chore(deps): update dependency pkg-up to v5
• chore(deps): update dependency write-file-atomic to v5
• chore(deps-dev): update actions/checkout action to v4
• chore(deps-dev): update actions/setup-node action to v4
• chore(deps-dev): update dependency @types/node to v20
• chore(deps-dev): update dependency @types/write-file-atomic to v4
• chore(deps-dev): update dependency typescript to v5
• chore(deps-dev): update github artifact actions to v4 (major) (actions/download-artifact, actions/upload-artifact)
• chore(deps-dev): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• chore(deps-dev): update linters (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-prettier, eslint-plugin-prettier, prettier)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/release.yml

• actions/checkout v3
• actions/setup-node v3
• actions/upload-artifact v3
• actions/checkout v3
• actions/setup-node v3
• actions/download-artifact v3

.github/workflows/test.yml

• actions/checkout v3
• actions/setup-node v3
• actions/checkout v3
• actions/setup-node v3
• actions/checkout v3
• actions/setup-node v3

npm

package.json

• mem ^8.1.1
• pkg-up ^3.1.0
• write-file-atomic ^3.0.3
• @types/jest ^28.1.8
• @types/node ^16.11.68
• @types/onetime ^4.0.0
• @types/pkg-up ^3.1.0
• @types/write-file-atomic ^3.0.3
• @typescript-eslint/eslint-plugin ^5.41.0
• @typescript-eslint/parser ^5.41.0
• eslint ^8.26.0
• eslint-config-prettier ^8.5.0
• eslint-plugin-prettier ^4.2.1
• jest ^28.1.3
• prettier ^2.7.1
• semantic-release 18.0.1
• ts-jest ^28.0.8
• typescript ^4.8.4

---

• Check this box to trigger a request for Renovate to run again on this repository

List all values

Hey 👋

I like this module a lot, it's nice and quick to use for scripts :)

It would be nice if it was possible to list all values stored. Is that something you would
accept a PR for?

Best,
Finn

Remove support for NodeJS v10.x

NodeJS v10.x is now EOL and supporting it is becoming harder.

• #198
  Upgrading to use Yarn v3 means that we can no longer develop or test on NodeJS v10.x. See migration notes.
• #210
  CI is no longer testing/linting/building on NodeJS v10 because of the above yarn v3 point so we cannot guarantee dotpref works on NodeJS v10.
• #219
  [email protected] has dropped support for NodeJS v10 as it is pure ESM.
• #230
  [email protected] has dropped support for NodeJS v10 as it is pure ESM.
• #269
  npm/[email protected] has dropped support for NodeJS v10.

Migrate to Pure ESM

Removing the support for NodeJS v10 and only supporting NodeJS v12 enables native ESM support.

2 of 3 dependencies for dotpref have migrated to pure ESM modules meaning dotpref cannot import them in its current form. Furthermore, semantic-release v19 includes ESM dependencies that yarn trips over resulting in pinning semantic-release to v18.

• #219
  [email protected] has dropped support for NodeJS v10 as it is pure ESM.
• #230
  [email protected] has dropped support for NodeJS v10 as it is pure ESM.

Currently, Jest support for ESM is experimental but even then, I couldn't get jest@27, ts-jest@27, and [email protected] to play nicely together using an ESM build. I'll revisit after jest@28 is released and try again.

Update June 22: jest@28 still only has experimental support for ESM, and I still can't get it working.

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: Invalid JSON (parsing failed)
Message: Syntax error: expecting end of expression or separator near "grou

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

The release 1.0.0 on branch master cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.0.0 <1.0.0 can be published from branch master.

The following commits are responsible for the invalid release:

• Update README.md (98d7d24)
• feat: tidy up based on initial feedback (fa1ce91)
• fix: update tsconfig and package.json to fix published files (4a0f1f8)
• fix: include and exclude the correct files for publishing to npm (2b9c018)
• chore: remove unused code and dry-run tag (56e3567)
• chore: prepare for initial release (0366301)
• Create LICENSE (613913f)
• chore: correct test.yml syntax (457daff)
• chore: update build, test, and release CI (88cb748)
• Update ci.yml (aeba692)
• Update ci.yml (2023991)
• Update ci.yml (7b6ffca)
• Update ci.yml (eca7e4f)
• Update cd.yml (11c51aa)
• chore: update cd file (1338488)
• chore: add cd file (b86c8c4)
• chore: add ci file (48c2406)
• chore: adding semantic release (8216d29)
• feat: adding code (f0cc660)
• chore: initial commit (9b617a0)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be master or next.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀