saravanakumardb1
83caf264df
chore: publish 8 outdated packages to Gitea registry
...
Published:
- @bytelyst/accessibility 0.1.6
- @bytelyst/billing-client 0.1.0 (new)
- @bytelyst/config 0.1.6
- @bytelyst/create-app 0.1.4
- @bytelyst/design-tokens 0.1.6
- @bytelyst/subscription-client 0.1.6
- @bytelyst/ui 0.1.8
- @bytelyst/webhook-dispatch 0.1.6
2026-05-14 17:35:04 -07:00
root
b6562b1de4
fix(ci): correct Gitea org name ByteLyst -> bytelyst in publish scripts
...
Generated with [Devin](https://cli.devin.ai/docs )
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-05-10 02:23:15 +00:00
saravanakumardb1
a107b2e342
fix: standardize common-plat .npmrc + publish script for corp network
...
- .npmrc: use ${GITEA_NPM_HOST:-localhost}:3300 (was hardcoded gitea.bytelyst.com)
- publish-local-packages.sh: use ${GITEA_NPM_HOST:-localhost}:3300 fallback
- fix-npmrc-all-repos.sh: add common-plat to repo list, skip self for
workspace link, add nested .npmrc scanning (e.g. dashboard/.npmrc)
2026-04-13 10:51:12 -07:00
saravanakumardb1
deff216c7e
refactor(gitea): robust manifest-based publish pipeline
...
publish-outdated-packages.sh rewritten:
- Manifest-based change detection (no registry tarball downloads)
- Single pack per package (not double-pack for check+publish)
- Deterministic content hash: normalizes version, publishConfig,
and @bytelyst/* dep versions (workspace:* resolution noise)
- Single metadata fetch per package (cached in-process)
- Fixed .npmrc overwrite bug that broke auth during publish phase
- npm_clean() helper strips all proxy env vars uniformly
release-packages.sh fixed:
- .npmrc now includes scoped registry + proxy=false for corp
- Unified corp/home publish path (no duplicated code)
- version_on_registry() uses proxy-stripped env
- Registry credential check uses proxy-stripped env
CI workflow: switched to publish-outdated-packages.sh --skip-build
2026-04-13 01:47:03 -07:00
saravanakumardb1
85bb860382
fix(gitea): fix publish auth — scoped registry + proxy=false in .npmrc
...
Root causes found:
1. publishConfig.registry in each package.json overrides --registry CLI
flag, causing npm to hit gitea.bytelyst.com through corp proxy.
2. Global ~/.npmrc proxy settings (NPM_CONFIG_PROXY env vars) route
localhost:3300 through the corporate proxy.
3. No .npmrc with auth token was created for npm publish to use.
Fix: generate a proper .npmrc in WORK_DIR with:
- _authToken for registry auth
- @bytelyst:registry scoped override (bypasses publishConfig)
- proxy=false + https-proxy=false on corp network
- Unified corp/home publish path (both use same .npmrc)
Token scope issue still open: current GITEA_NPM_TOKEN has read:package
but not write:package — needs regeneration in Gitea UI.
2026-04-13 00:21:13 -07:00
saravanakumardb1
54a06e227a
refactor(scripts): move 5 Gitea scripts into scripts/gitea/ subdirectory
...
Moved:
publish-local-gitea-packages.sh → gitea/publish-local-packages.sh
publish-outdated-gitea-packages.sh → gitea/publish-outdated-packages.sh
release-gitea-packages.sh → gitea/release-packages.sh
run-registry-tests.sh → gitea/run-registry-tests.sh
harden-publish-config.sh → gitea/harden-publish-config.sh
Dropped -gitea- infix (redundant with folder name).
Fixed in every moved script:
- REPO_ROOT: ../ → ../../ (one level deeper)
- Internal cross-reference comments
Updated all 10 referencing files:
- package.json (release script path)
- .gitea/workflows/ci.yml (publish step)
- 3 workflow .md files (publish-outdated usage)
- 3 devops docs (publish-local + registry-tests refs)
- 2 internal comment cross-references
2026-04-13 00:02:55 -07:00
