semantic-release / npm-registry-docker

:ship: CouchDB Docker image running npm-registry-couchapp

semanticrelease/npm-registry-docker

CouchDB Docker image running npm-registry-couchapp.

This docker image is for test and development purposes only.

Install

$ docker pull semanticrelease/npm-registry-docker:latest

Usage

With default environment variables

$ docker run -d -p 5984:5984 semanticrelease/npm-registry-docker

The npm registry is accessible on http://localhost:5984/registry/_design/app/_rewrite and the CouchDB user admin with password admin is created.

To configure npm to use the registry:

$ npm config set registry http://localhost:5984/registry/_design/app/_rewrite

To create a npm user and configure npm authentication:

$ curl -H 'Content-Type: application/json' -XPUT -d '{"_id": "org.couchdb.user:npm-user","name": "npm-user","roles": [],"type": "user","password": "npm-password","email":  "[email protected]"}' "http://admin:admin@localhost:5984/_users/org.couchdb.user:npm-user"

$ echo "_auth = $(echo -n npm-user:npm-password | base64)" >> .npmrc
$ echo "email = [email protected]" >> .npmrc

With custom admin user and vhost configuration

$ docker run -d -p 5984:5984 -e COUCHDB_USER=my-user -e COUCHDB_PASSWORD=my-password -e VHOST=my-registry.com semanticrelease/npm-registry-docker

The npm registry is accessible on http://my-registry:5984 and the CouchDB user my-user with password my-password is created.

To configure npm to use the registry:

$ npm config set registry http://my-registry:5984

To create a npm user and configure npm authentication:

$ curl -H 'Content-Type: application/json' -XPUT -d '{"_id": "org.couchdb.user:npm-user","name": "npm-user","roles": [],"type": "user","password": "npm-password","email":  "[email protected]"}' "http://my-user:my-password@localhost:5984/_users/org.couchdb.user:npm-user"

$ echo "_auth = $(echo -n npm-user:npm-password | base64)" >> .npmrc
$ echo "email = [email protected]" >> .npmrc

npm-registry-docker's Issues

An in-range update of semantic-release is breaking the build 🚨

Version 15.9.6 of semantic-release was just published.

Branch	Build failing 🚨
Dependency	semantic-release
Current Version	15.9.5
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ❌ Travis CI - Branch: The build failed.

---

Release Notes

v15.9.6

15.9.6 (2018-08-08)

Bug Fixes

• do not convert ssh repositoryUrl to https (b895231)

Commits

The new version differs by 3 commits.

• b895231 fix: do not convert ssh repositoryUrl to https
• 8b8e40c docs(plugins): add semantic-release-firefox
• 06695a1 chore(package): update xo to version 0.22.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

replace travis with actions

Part of semantic-release/semantic-release#1692

Todos

• delete .travis.yml
• create .github/workflows/{test,release}.yml (copy from https://github.com/semantic-release/npm/tree/master/.github/workflows)
• remove package-lock.json from .gitignore
• delete .npmrc and .yarnrc
• README
  • remove travis/codecov badges
  • add actions badge instead (replace REPO NAME HERE ;): [![Build Status](https://github.com/semantic-release/[REPO NAME HERE]/workflows/Test/badge.svg)](https://github.com/semantic-release/[REPO NAME HERE]/actions?query=workflow%3ATest+branch%3Amaster)
• create package-json.lock
• add to package.json:

  • test:ci script which doesn't run lint pre script

  • renovate config

       "renovate": {
         "extends": [
           "github>semantic-release/.github"
         ]
       }
    

• update branch protection: remove required status by Travis and Codecov, add required status for "test" (wait for first build of PR)

An in-range update of ava is breaking the build 🚨

The devDependency ava was updated from 1.4.0 to 1.4.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ava is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for 1.4.1

Focusing power-assert

AVA comes with power-assert built-in, giving you more descriptive assertion messages. However it's been confusing to understand which assertions come with power-assert. To address this we've added the new t.assert() assertion. It's now the only assertion that is power-assert enabled. The assertion passes if called with a truthy value. Consider this example:

test('enhanced assertions', t => {
	const a = /foo/;
	const b = 'bar';
	const c = 'baz';
	t.assert(a.test(b) || b === c);
});

AVA will output:

6:   const c = 'baz';
7:   t.assert(a.test(b) || b === c);
8: });
Value is not truthy:
false
a.test(b) || b === c

=> false
b === c

=> false
c

=> 'baz'
b

=> 'bar'
a.test(b)

=> false
b

=> 'bar'
a

=> /foo/

Our ESLint plugin has been updated to support this new assertion. Many thanks to @eemed for implementing this! 9406470

Watch mode

Watch mode now prints the available commands. Thanks @KompKK! cd256ac

Bug fixes

• Filtered tests (when using --match, .skip() or .only()) are no longer included in the list of pending tests when timeouts occur or when you interrupt a test run. Thanks @vancouverwill! 23e302a
• We're now shimming all TTY methods in the worker processes, thanks to @okyantoro. c1f6fdf

Documentation updates

• We've added a note to say that, by default, AVA does not have a default test timeout. Thanks @amokmen! 99a10a1

All changes

v1.3.1...v1.4.1

Thanks

Thank you @eemed, @KompKK, @vancouverwill, @okyantoro and @amokmen. We couldn't have done this without you!

Get involved

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

Commits

The new version differs by 3 commits.

• 9ef456b 1.4.1
• 55d973d Tweak reporter integration tests so they pass on Node.js 12-pre
• a7605de Add t.assert() to type definitions

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

replace travis with actions

Part of semantic-release/semantic-release#1692

Todos

• delete .travis.yml
• create .github/workflows/{test,release}.yml (copy from https://github.com/semantic-release/npm/tree/master/.github/workflows)
• remove package-lock.json from .gitignore
• delete .npmrc and .yarnrc
• README
  • remove travis/codecov badges
  • add actions badge instead (replace REPO NAME HERE ;): [![Build Status](https://github.com/semantic-release/[REPO NAME HERE]/workflows/Test/badge.svg)](https://github.com/semantic-release/[REPO NAME HERE]/actions?query=workflow%3ATest+branch%3Amaster)
• create package-json.lock
• add to package.json:

  • test:ci script which doesn't run lint pre script

  • renovate config

       "renovate": {
         "extends": [
           "github>semantic-release/.github"
         ]
       }
    

• update branch protection: remove required status by Travis and Codecov, add required status for "test" (wait for first build of PR)

An in-range update of @semantic-release/exec is breaking the build 🚨

Version 3.0.2 of @semantic-release/exec was just published.

Branch	Build failing 🚨
Dependency	@semantic-release/exec
Current Version	3.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@semantic-release/exec is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ❌ Travis CI - Branch: The build failed.

---

Release Notes

v3.0.2

3.0.2 (2018-08-08)

Bug Fixes

• verify the cmd config independently for each steps (0fee76f)

Commits

The new version differs by 2 commits.

• 0fee76f fix: verify the cmd config independently for each steps
• 06d1a74 chore(package): update xo to version 0.22.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Dependency Dashboard

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

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency tempy to ^0.7.0
• chore(deps): update dependency xo to ^0.39.0
• chore(deps): update actions/checkout action to v3
• chore(deps): update actions/setup-node action to v3
• chore(deps): update apache/couchdb docker tag to v3
• chore(deps): update dependency ava to v5
• chore(deps): update dependency delay to v5
• chore(deps): update dependency execa to v6
• chore(deps): update dependency fs-extra to v10
• chore(deps): update dependency got to v12
• chore(deps): update dependency p-retry to v5
• chore(deps): update dependency tempy to v1
• chore(deps): update semantic-release monorepo (major) (@semantic-release/exec, @semantic-release/github, semantic-release)
• 🔐 Create all rate-limited PRs at once 🔐

Open

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

• chore(deps): update dependency ansi-regex [security]
• chore(deps): update dependency axios to 0.21.2 [security]
• chore(deps): update dependency elliptic to 6.5.4 [security]
• chore(deps): update dependency follow-redirects to 1.14.8 [security]
• chore(deps): update dependency glob-parent to 5.1.2 [security]
• chore(deps): update dependency got to 11.8.5 [security]
• chore(deps): update dependency handlebars to 4.7.7 [security]
• chore(deps): update dependency hosted-git-info [security]
• chore(deps): update dependency ini to 1.3.6 [security]
• chore(deps): update dependency lodash to 4.17.21 [security]
• chore(deps): update dependency marked to 4.0.10 [security]
• chore(deps): update dependency node-fetch to 2.6.7 [security]
• chore(deps): update dependency normalize-url [security]
• chore(deps): update dependency path-parse to 1.0.7 [security]
• chore(deps): update dependency semantic-release to 19.0.3 [security]
• chore(deps): update dependency semver-regex to 3.1.4 [security]
• chore(deps): update dependency ssh2 to 1.4.0 [security]
• chore(deps): update dependency trim-newlines to 3.0.1 [security]
• chore(deps): update dependency trim-off-newlines to 1.0.3 [security]
• chore(deps): update dependency yargs-parser to 13.1.2 [security]
• chore(deps): lock file maintenance
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

dockerfile

Dockerfile

• apache/couchdb 2.3
• apache/couchdb 2.3

github-actions

.github/workflows/release.yml

• actions/checkout v2
• actions/setup-node v1
• bahmutov/npm-install v1

.github/workflows/test.yml

• actions/checkout v2
• actions/setup-node v2
• actions/checkout v2
• actions/setup-node v2

npm

package.json

• npm-registry-couchapp ^3.0.0
• @semantic-release/exec ^5.0.0
• @semantic-release/github ^7.0.0
• ava ^3.1.0
• delay ^4.0.0
• dockerode ^3.0.0
• execa ^4.0.0
• fs-extra ^9.0.0
• got ^10.0.0
• p-retry ^4.0.0
• semantic-release ^17.0.0
• tempy ^0.5.0
• xo ^0.28.0

---

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

An in-range update of delay is breaking the build 🚨

The devDependency delay was updated from 4.1.0 to 4.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

delay is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v4.2.0

• Refactor TypeScript definition to CommonJS compatible export (#44) fa2d83c

v4.1.0...v4.2.0

Commits

The new version differs by 2 commits.

• 37c832b 4.2.0
• fa2d83c Refactor TypeScript definition to CommonJS compatible export (#44)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of p-retry is breaking the build 🚨

The devDependency p-retry was updated from 4.0.0 to 4.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

p-retry is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v4.1.0

• Refactor TypeScript definition to CommonJS compatible export (#23) 71e51ad

v4.0.0...v4.1.0

Commits

The new version differs by 2 commits.

• 9e2c016 4.1.0
• 71e51ad Refactor TypeScript definition to CommonJS compatible export (#23)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Fix "connect ENOENT /var/run/docker.sock" error when running tests

I see the error both locally and on CI

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.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)