ci-delta - npm Package Compare versions

Comparing version

0.1.1

0.1.2

+12

-1

package.json

		{
		"name": "ci-delta",
		"version": "0.1.1",
		"version": "0.1.2",
		"description": "Semantic diff reports for CI/CD config changes",
		@@ -10,2 +10,13 @@ "type": "module",
		},
		"repository": {
		"type": "git",
		"url": "git+https://github.com/tengfone/ci-delta.git"
		},
		"bugs": {
		"url": "https://github.com/tengfone/ci-delta/issues"
		},
		"homepage": "https://github.com/tengfone/ci-delta#readme",
		"publishConfig": {
		"access": "public"
		},
		"engines": {
		@@ -12,0 +23,0 @@ "node": ">=20"

+31

-1

README.md

		# ci-delta

		[![CI](https://github.com/tengfone/ci-delta/actions/workflows/ci.yml/badge.svg)](https://github.com/tengfone/ci-delta/actions/workflows/ci.yml)
		[![Release](https://img.shields.io/github/v/release/tengfone/ci-delta?sort=semver)](https://github.com/tengfone/ci-delta/releases)
		[![npm](https://img.shields.io/npm/v/ci-delta)](https://www.npmjs.com/package/ci-delta)
		[![GitHub Marketplace](https://img.shields.io/badge/GitHub%20Marketplace-ci--delta-0969da?logo=github)](https://github.com/marketplace/actions/ci-delta)

		[GitHub repository](https://github.com/tengfone/ci-delta)

		Semantic diff reports for CI/CD config changes.
		@@ -29,3 +36,3 @@

		Install or run with npm:
		Run the CLI with npm:

		@@ -120,2 +127,5 @@ ```bash

		See a real smoke-test PR and sticky report:
		[tengfone/ci-delta#5](https://github.com/tengfone/ci-delta/pull/5#issuecomment-4275678904).

		```md
		@@ -210,2 +220,22 @@ ## CI Delta Report

		## Release Process

		Stable releases are driven by GitHub Releases:

		1. Update `package.json` to the next stable semver version and merge to `main`.
		2. Create and publish a GitHub Release whose tag exactly matches the package version, such as `v0.1.2`.
		3. The `Release` workflow verifies the tag, runs the production package gates, publishes the package to npm, and moves the matching major action tag, such as `v0`.

		Prereleases are not published automatically yet. Keep `v*` release tags protected with GitHub repository rules so only maintainers can create or move release tags.

		Before using automated npm publishing, configure npm Trusted Publishing for this package:

		- Publisher: GitHub Actions
		- Organization or user: `tengfone`
		- Repository: `ci-delta`
		- Workflow filename: `release.yml`
		- Environment: leave blank

		The release workflow uses GitHub OIDC for npm publishing. Do not store a long-lived npm publish token in repository secrets.

		## Limitations
		@@ -212,0 +242,0 @@

ci-delta - npm Package Compare versions

Fixed alerts

Improved metrics