@mereb/shared-packages 0.0.5 → 0.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
# Shared Mereb Backend Packages
|
|
2
2
|
|
|
3
|
-
This package exposes the shared Fastify/OpenTelemetry helpers used across the backend services. It is built independently with TypeScript and published as `@
|
|
3
|
+
This package exposes the shared Fastify/OpenTelemetry helpers used across the backend services. It is built independently with TypeScript and published as `@mereb/shared-packages`.
|
|
4
4
|
|
|
5
5
|
## Local development
|
|
6
6
|
|
|
7
7
|
```bash
|
|
8
8
|
pnpm install
|
|
9
|
-
pnpm --filter @
|
|
10
|
-
pnpm --filter @
|
|
11
|
-
pnpm --filter @
|
|
9
|
+
pnpm --filter @mereb/shared-packages lint
|
|
10
|
+
pnpm --filter @mereb/shared-packages typecheck
|
|
11
|
+
pnpm --filter @mereb/shared-packages build
|
|
12
12
|
```
|
|
13
13
|
|
|
14
14
|
The compiled JavaScript and type definitions land in `dist/`.
|
|
@@ -17,7 +17,7 @@ The compiled JavaScript and type definitions land in `dist/`.
|
|
|
17
17
|
|
|
18
18
|
The folder contains its own `Jenkinsfile` plus `.ci/ci.yml` so it can run through the `mereb-jenkins` shared library just like the services do.
|
|
19
19
|
|
|
20
|
-
1. **Version bump** – run `pnpm --filter @
|
|
20
|
+
1. **Version bump** – run `pnpm --filter @mereb/shared-packages version:bump` (optionally pass `major` or `minor`). The script inspects the latest `v*` tag and updates `package.json` to the next version so the release tag and package stay in sync.
|
|
21
21
|
2. **Push to `main`** – Jenkins runs the branch build. After it lints/builds, the `release.autoTag` stage (configured with `allowDirty: true` because the build leaves `node_modules/` around) creates and pushes the next `v<semver>` tag.
|
|
22
22
|
3. **Release stages** – in the same build, the new `releaseStages` block uses that tag (`RELEASE_TAG`) to run `pnpm publish` and then the `release.github` stage publishes release notes.
|
|
23
23
|
4. **Jenkins job** – create a Multibranch Pipeline pointing at this repository. Tags are optional now, but still enable tag discovery if you want Jenkins to react to manual tags.
|
|
@@ -26,7 +26,7 @@ The folder contains its own `Jenkinsfile` plus `.ci/ci.yml` so it can run throug
|
|
|
26
26
|
|
|
27
27
|
Every successful `main` build with a version bump now produces a tag, publishes the package, and creates GitHub release notes without waiting for a second job.
|
|
28
28
|
|
|
29
|
-
> Tip: The bump script accepts `major`, `minor`, or `patch` (default) so you can control which segment changes: `pnpm --filter @
|
|
29
|
+
> Tip: The bump script accepts `major`, `minor`, or `patch` (default) so you can control which segment changes: `pnpm --filter @mereb/shared-packages version:bump minor`.
|
|
30
30
|
|
|
31
31
|
> The repo installs a Husky `pre-commit` hook that automatically runs `pnpm run version:bump` and stages `services/shared/package.json`, keeping the version aligned with the next release tag before every commit. Jenkins sets `HUSKY=0` (see `.ci/ci.yml`) so the hook never runs in CI; locally you can bypass it with `HUSKY=0 git commit ...`.
|
|
32
32
|
|