Compare commits

...

4 Commits

Author SHA1 Message Date
49cfcaedd1 4.3.4
Some checks failed
Default (tags) / security (push) Successful in 34s
Default (tags) / test (push) Successful in 1m1s
Default (tags) / release (push) Failing after 46s
Default (tags) / metadata (push) Successful in 56s
2025-10-25 17:16:01 +00:00
3996a69f91 fix(ci): Fix Gitea workflow publish invocation to run npm publish via npmci command 2025-10-25 17:16:01 +00:00
629f6dd425 4.3.3
Some checks failed
Default (tags) / security (push) Successful in 43s
Default (tags) / test (push) Successful in 1m5s
Default (tags) / release (push) Failing after 48s
Default (tags) / metadata (push) Successful in 57s
2025-10-25 17:09:33 +00:00
d141ceeaf7 fix(ci): Improve Gitea release workflow: install deps, configure Gitea npm registry, and optionally publish to npmjs.org 2025-10-25 17:09:33 +00:00
4 changed files with 31 additions and 3 deletions

View File

@@ -88,7 +88,20 @@ jobs:
- name: Release
run: |
npmci node install stable
npmci npm install
# Extract server host from GITHUB_SERVER_URL (remove https://)
GITEA_HOST="${GITHUB_SERVER_URL#https://}"
GITEA_REGISTRY="$GITHUB_SERVER_URL/api/packages/$GITHUB_REPOSITORY_OWNER/npm/"
# Configure Gitea npm registry
npmci command npm config set @${GITHUB_REPOSITORY_OWNER}:registry "$GITEA_REGISTRY"
npmci command npm config set "//${GITEA_HOST}/api/packages/${GITHUB_REPOSITORY_OWNER}/npm/:_authToken" "$GITEA_TOKEN"
# Publish to Gitea
npmci command npm publish
# Conditionally publish to npmjs.org if token exists
if [ -n "$NPMCI_TOKEN_NPM" ]; then
npmci command npm config set registry https://registry.npmjs.org
npmci npm publish
fi
metadata:
needs: test

View File

@@ -1,5 +1,20 @@
# Changelog
## 2025-10-25 - 4.3.4 - fix(ci)
Fix Gitea workflow publish invocation to run npm publish via npmci command
- Update .gitea/workflows/default_tags.yaml to use 'npmci command npm publish' for the publish step
- Ensures the workflow runs npm publish through the npmci command wrapper to avoid incorrect task invocation
## 2025-10-25 - 4.3.3 - fix(ci)
Improve Gitea release workflow: install deps, configure Gitea npm registry, and optionally publish to npmjs.org
- Run npm install in the release job to ensure dependencies are available before publishing.
- Configure Gitea/npm registry using GITHUB_SERVER_URL and set auth token for the @<owner> scope.
- Publish to the Gitea npm registry during release.
- If NPMCI_TOKEN_NPM is provided, also publish to the public npmjs.org registry (conditional publish).
- Extract host from GITHUB_SERVER_URL to correctly set the registry auth URL.
## 2025-10-17 - 4.3.2 - fix(core)
Remove stray console.log from core module

View File

@@ -1,6 +1,6 @@
{
"name": "@push.rocks/smartrequest",
"version": "4.3.2",
"version": "4.3.4",
"private": false,
"description": "A module for modern HTTP/HTTPS requests with support for form data, file uploads, JSON, binary data, streams, and more.",
"exports": {

View File

@@ -3,6 +3,6 @@
*/
export const commitinfo = {
name: '@push.rocks/smartrequest',
version: '4.3.2',
version: '4.3.4',
description: 'A module for modern HTTP/HTTPS requests with support for form data, file uploads, JSON, binary data, streams, and more.'
}