Big News: Socket raises $60M Series C at a $1B valuation to secure software supply chains for AI-driven development.Announcement
Sign In

ep_clear_formatting

Package Overview
Dependencies
Maintainers
5
Versions
49
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

ep_clear_formatting - npm Package Compare versions

Comparing version
0.0.36
to
0.0.38
+16
-2
.github/workflows/npmpublish.yml

@@ -18,3 +18,3 @@ # This workflow will run tests using node and then publish a package to the npm registry when a release is created

permissions:
contents: write # for `git push --follow-tags` of the version bump
contents: write # for the atomic version-bump push (branch + tag)
id-token: write # for npm OIDC trusted publishing

@@ -64,4 +64,18 @@ steps:

pnpm i
# `pnpm version patch` bumps package.json, makes a commit, and creates
# a `v<new-version>` tag. Capture the new tag name from package.json
# rather than parsing pnpm's output, which has historically varied.
pnpm version patch
git push --follow-tags
NEW_TAG="v$(node -p "require('./package.json').version")"
# CRITICAL: use --atomic so the branch update and the tag update
# succeed (or fail) as a single transaction on the server. The old
# `git push --follow-tags` was non-atomic per ref: if a concurrent
# publish run won the race, the branch fast-forward would be rejected
# but the tag push would still land — leaving a dangling tag with no
# matching commit on the branch. Subsequent runs would then forever
# try to bump to the same already-existing tag and fail with
# `tag 'vN+1' already exists`. With --atomic, a rejected branch push
# rejects the tag push too, and the next workflow tick can retry
# cleanly against the up-to-date refs.
git push --atomic origin "${GITHUB_REF_NAME}" "${NEW_TAG}"
# This is required if the package has a prepare script that uses something

@@ -68,0 +82,0 @@ # in dependencies or devDependencies.

+1
-1
{
"name": "ep_clear_formatting",
"version": "0.0.36",
"version": "0.0.38",
"keywords": [

@@ -5,0 +5,0 @@ "clear",