@edsis/angular

Angular library package for Edsis, including the generated SDK entry points:

• @edsis/angular/auth
• @edsis/angular/sdk
• @edsis/angular/sdk/shared
• @edsis/angular/sdk/access
• @edsis/angular/sdk/approval
• @edsis/angular/sdk/auth
• @edsis/angular/sdk/employee
• @edsis/angular/sdk/health
• @edsis/angular/sdk/storage
• @edsis/angular/sdk/user

Generate and build

Use the root workspace scripts so SDK generation and library packaging stay in sync:

bun run build:library

That command runs:

bun run gen:sdk
bunx ng build library

The packaged output is written to dist/library, including the reusable @edsis/angular/auth entry point.

Full release

Run the guarded release flow with:

bun run release:library

The script will:

• reject the release if the git worktree is dirty
• reject the release if the current branch still has commits that are not pushed, is behind, or is diverged from its upstream branch
• ask for a version bump using X, Y, or Z
• map X to major, Y to minor, and Z to patch, then increment the current version automatically
• ask for a final confirmation before continuing
• run bun run build:library
• commit the version bump and generated SDK updates with update version ke {{version}}
• push the commit
• publish dist/library to the public npm registry

For a non-interactive release, provide the bump and confirmation flags explicitly:

bun run release:library --bump Z --yes

Preview the release plan without changing files:

bun run release:library:dry-run --bump Y --yes

Versioning

Update the publishable package version in projects/library/package.json with:

bun run version:library patch
bun run version:library minor
bun run version:library 1.2.3
bun run version:library prerelease --preid beta

The version script only updates the source package manifest. The built package in dist/library picks up the version on the next bun run build:library.

Pack and publish locally

Run the interactive local publish workflow with:

bun run publish

The script will:

• verify the active npm login against the public npm registry
• ask for a version bump using X, Y, or Z
• update projects/library/package.json
• run bun run build:library
• publish dist/library to npm public with --access public

For a non-interactive publish, provide the bump and confirmation flags explicitly:

bun run publish --bump Z --yes

Preview the publish plan without changing files:

bun run publish --dry-run --bump Y --yes

Preview the npm tarball:

bun run pack:library

Publish to npm:

bun run publish:library
bun run publish:library --tag next

Run a local publish dry-run:

bun run publish:library:dry-run

When updating @ojiepermana/angular, use the helper below instead of a plain bun update so the version pin, patch mapping, install step, and SDK build verification stay in sync:

bun run update:ojiepermana

If a specific version needs to be tested:

bun run update:ojiepermana 21.1.11

publish:library publishes from dist/library and forces --access public.

For local publishes, the script does not add --provenance by default because npm provenance generation is not supported outside compatible CI providers. If you need provenance in a supported CI environment, pass it explicitly:

bun run publish:library --provenance

GitHub publish workflow

The repository includes .github/workflows/publish-library.yml.

It supports:

• pushing a tag named library-vX.Y.Z
• manual workflow_dispatch runs with an npm tag and optional dry-run

The workflow uses npm trusted publishing via GitHub Actions OIDC, so it does not require a repository NPM_TOKEN secret. The npm package must be configured to trust this repository workflow as a publisher. On tag pushes, the tag version must match projects/library/package.json.

Recommended local release flow:

1. Run bun run release:library.
2. Select X, Y, or Z, then confirm the computed version.
3. Let the script build, commit, push, and publish the package.