Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Performing a release does not correctly update NPM package files #876

Open
adamretter opened this issue Jan 4, 2023 · 0 comments
Open
Labels

Comments

@adamretter
Copy link
Contributor

After a performing a release there is also the issue that these two files are changed and unstaged and need to be manually committed and pushed separately - which breaks the atomic release commit concept:

diff --git a/package-lock.json b/package-lock.json
index 5f25e11..91b5029 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "exist-documentation",
-  "version": "5.4.1-SNAPSHOT",
+  "version": "6.1.0",
   "lockfileVersion": 2,
   "requires": true,
   "packages": {
     "": {
       "name": "exist-documentation",
-      "version": "5.4.1-SNAPSHOT",
+      "version": "6.1.0",
       "license": "LGPL-2.1-only",
       "dependencies": {
         "@neos21/bootstrap3-glyphicons": "^1.0.7",
diff --git a/package.json b/package.json
index 2e35c26..f1238cf 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "exist-documentation",
-  "version": "5.4.1-SNAPSHOT",
+  "version": "6.1.0",
   "description": "Documentation package for eXist-db",
   "scripts": {
     "test": "mocha src/test/mocha/ --recursive --exit",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant