[PR #72] [MERGED] Add automatic npm publish workflow #63

Closed
opened 2026-05-23 08:35:40 -06:00 by gitea-mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/appy-one/acebase-client/pull/72
Author: @appy-one
Created: 4/14/2026
Status: Merged
Merged: 4/16/2026
Merged by: @appy-one

Base: masterHead: add-publish-workflow


📝 Commits (10+)

  • 6d6d505 Add GitHub actions publish workflow
  • 86c45dc Change acebase-core dependency to file for development (automatically replaced by latest package upon publish)
  • da122a1 update browser example to use async flow instead of promise chain
  • 7058dd1 bump acebase dependencies
  • b23a249 new test build
  • 4ca8ae5 ignore .DS_Store
  • ebba9f4 chore: release v1.22.3-rc.1 [skip ci]
  • 4821683 Add next flag for RC dry runs of npm publish
  • 37c22c5 chore: release v1.22.3-rc.2 [skip ci]
  • 8ca0928 Normalize repository property to remove npm warning

📊 Changes

13 files changed (+380 additions, -265 deletions)

View changed files

.github/workflows/publish.yml (+125 -0)
📝 .gitignore (+1 -0)
📝 package-lock.json (+34 -45)
📝 package.json (+6 -3)
📝 src/browser.html (+12 -17)
📝 test/cjs/cache.js (+28 -28)
📝 test/cjs/run.js (+61 -61)
📝 test/cjs/settings.js (+8 -8)
📝 test/esm/cache.js (+24 -24)
📝 test/esm/run.js (+56 -56)
📝 test/esm/settings.js (+5 -5)
📝 test/package-lock.json (+18 -16)
📝 test/package.json (+2 -2)

📄 Description

This adds an automatic npm publish workflow upon tag push


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/appy-one/acebase-client/pull/72 **Author:** [@appy-one](https://github.com/appy-one) **Created:** 4/14/2026 **Status:** ✅ Merged **Merged:** 4/16/2026 **Merged by:** [@appy-one](https://github.com/appy-one) **Base:** `master` ← **Head:** `add-publish-workflow` --- ### 📝 Commits (10+) - [`6d6d505`](https://github.com/appy-one/acebase-client/commit/6d6d5051fb43c590e786b0ad3738bee379eaa4fd) Add GitHub actions publish workflow - [`86c45dc`](https://github.com/appy-one/acebase-client/commit/86c45dc25e67d1d4323c905d5cf2c3633999dbf8) Change acebase-core dependency to file for development (automatically replaced by latest package upon publish) - [`da122a1`](https://github.com/appy-one/acebase-client/commit/da122a1413391dc18520d3e4bc22ed560db4976d) update browser example to use async flow instead of promise chain - [`7058dd1`](https://github.com/appy-one/acebase-client/commit/7058dd1cb522f0a428498d1e684c4f188bf75020) bump acebase dependencies - [`b23a249`](https://github.com/appy-one/acebase-client/commit/b23a24929f5e804aadd20b194ac0a8e847059790) new test build - [`4ca8ae5`](https://github.com/appy-one/acebase-client/commit/4ca8ae5355c18ed4a71289c14358b5425bed84fa) ignore .DS_Store - [`ebba9f4`](https://github.com/appy-one/acebase-client/commit/ebba9f45b651e7b0db0aa635b59633c194153a13) chore: release v1.22.3-rc.1 [skip ci] - [`4821683`](https://github.com/appy-one/acebase-client/commit/482168383c3aef981e6129b9e85e746ee9cc7521) Add next flag for RC dry runs of npm publish - [`37c22c5`](https://github.com/appy-one/acebase-client/commit/37c22c5c48d3e9e39a26b6797f22e9193e5a66fc) chore: release v1.22.3-rc.2 [skip ci] - [`8ca0928`](https://github.com/appy-one/acebase-client/commit/8ca0928ec860b60de9da248673890f7d762fff57) Normalize `repository` property to remove npm warning ### 📊 Changes **13 files changed** (+380 additions, -265 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/publish.yml` (+125 -0) 📝 `.gitignore` (+1 -0) 📝 `package-lock.json` (+34 -45) 📝 `package.json` (+6 -3) 📝 `src/browser.html` (+12 -17) 📝 `test/cjs/cache.js` (+28 -28) 📝 `test/cjs/run.js` (+61 -61) 📝 `test/cjs/settings.js` (+8 -8) 📝 `test/esm/cache.js` (+24 -24) 📝 `test/esm/run.js` (+56 -56) 📝 `test/esm/settings.js` (+5 -5) 📝 `test/package-lock.json` (+18 -16) 📝 `test/package.json` (+2 -2) </details> ### 📄 Description This adds an automatic npm publish workflow upon tag push --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
gitea-mirror 2026-05-23 08:35:40 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/acebase-client#63
No description provided.