gh-upload-file 0.12.1 → 0.13.1

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.
Files changed (3) hide show
  1. package/CHANGELOG.md +18 -0
  2. package/README.md +3 -4
  3. package/package.json +1 -41
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # gh-upload-log
2
2
 
3
+ ## 0.13.1
4
+
5
+ ### Patch Changes
6
+
7
+ - 4003e97: Recover partial releases from the original workflow SHA without consuming newer changesets or bumping again. Give npm consumer installation a bounded 25-minute visibility window with fresh metadata, preserve install diagnostics and fail promptly on permanent errors. Create missing GitHub releases from the exact version commit.
8
+
9
+ ## 0.13.0
10
+
11
+ ### Minor Changes
12
+
13
+ - Fix CI/CD false positives, false negatives and warnings: release scripts now fail on any failed git, npm or gh command instead of reporting success, and no longer evaluate code downloaded from unpkg. GitHub release notes are published as Changesets wrote them (nested lists, later entries and text after `---` are no longer dropped, every entry's pull request is linked), the npm badges no longer render as "badge not found", and a release reads exactly its own CHANGELOG.md section. The workflow adopts the pipeline template's practices (change detection, a pipeline-status gate, release preflight annotations, pinned runners and actions, per-job timeouts and concurrency, secret scanning, Markdown link checking, documentation and file-size checks, actionlint, ShellCheck, zizmor, CodeQL and dependency audits), and the lockfiles no longer contain known high or moderate advisories.
14
+
15
+ The release step now fails when GitHub refuses to create the release (under Bun, command-stream 0.7.1 reported exit code 0 for a failing command fed through stdin), a version-commit push that lost a race with another merge is rebased and retried while a push refused by a repository rule fails at once with the rule's output, npm publication is verified for up to 25 minutes and an E409 "already published" answer counts as landed, and a release that died after the version commit or the publish is finished by the next push to main instead of being forgotten.
16
+
17
+ Authentication and registry errors (E404, E401, E403, ENEEDAUTH) from `npm publish` are no longer retried, every published npm name is installed from the registry and smoke-tested (each bin's `--help` and the library import) before the GitHub release is created, and shell scripts and the git hook keep LF line endings on Windows checkouts, where CRLF made Bash fail with `set: pipefail\r: invalid option name`.
18
+
19
+ Sanitize every upload with sensitive-data-sanitizer in streaming credentials-only mode, preserving public account details and binary bytes while reporting rule counts. Block uploads on sanitization errors. Check npm package bootstrap before versioning releases, retain synchronized gh-upload-log publication, and document required npm owner recovery steps.
20
+
3
21
  ## 0.12.1
4
22
 
5
23
  ### Patch Changes
package/README.md CHANGED
@@ -679,10 +679,9 @@ node experiments/issue-37-package-smoke.mjs
679
679
  ```
680
680
 
681
681
  Both automatic and manual releases check npm package existence before versioning.
682
- The first `gh-upload-file` publication and trusted publisher setup require an
683
- authorized npm account. Follow the [exact recovery procedure](./docs/npm-publishing.md),
684
- which preserves synchronized `gh-upload-log` releases. Publication remains
685
- blocked until those owner steps are completed.
682
+ Both package names are published through OIDC as of 0.13.0. The
683
+ [release recovery procedure](./docs/npm-publishing.md) explains bounded registry
684
+ visibility retries and resuming an interrupted release without another version bump.
686
685
 
687
686
  ## Contributing
688
687
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "gh-upload-file",
3
- "version": "0.12.1",
3
+ "version": "0.13.1",
4
4
  "description": "Upload text and binary files to GitHub as Gists or chunked repository archives",
5
5
  "type": "module",
6
6
  "main": "src/index.js",
@@ -9,21 +9,6 @@
9
9
  "gh-upload-file": "src/cli.js",
10
10
  "gh-upload-log": "src/cli.js"
11
11
  },
12
- "scripts": {
13
- "test": "bun test --timeout 30000",
14
- "lint": "eslint . --max-warnings 0",
15
- "lint:fix": "eslint . --fix",
16
- "format": "prettier --write .",
17
- "format:check": "prettier --check .",
18
- "check:file-size": "bun scripts/check-file-size.mjs",
19
- "check:docs": "node scripts/check-required-docs.mjs",
20
- "check": "bun run lint && bun run format:check && bun run check:file-size && bun run check:docs",
21
- "prepare": "node scripts/install-git-hooks.mjs",
22
- "changeset": "changeset",
23
- "changeset:version": "bun scripts/changeset-version.mjs",
24
- "changeset:publish": "bun scripts/publish-to-npm.mjs",
25
- "changeset:status": "changeset status --since=origin/main"
26
- },
27
12
  "keywords": [
28
13
  "github",
29
14
  "gist",
@@ -51,31 +36,6 @@
51
36
  "use-m": "^8.13.7",
52
37
  "yargs": "^17.7.2"
53
38
  },
54
- "devDependencies": {
55
- "@changesets/changelog-github": "^0.5.1",
56
- "@changesets/cli": "^2.29.7",
57
- "eslint": "^9.38.0",
58
- "eslint-config-prettier": "^10.1.8",
59
- "eslint-plugin-prettier": "^5.5.4",
60
- "husky": "^9.1.7",
61
- "lint-staged": "^16.2.6",
62
- "prettier": "^3.6.2",
63
- "test-anywhere": "^0.8.48"
64
- },
65
- "lint-staged": {
66
- "*.{js,mjs,cjs}": [
67
- "eslint --fix --max-warnings 0 --no-warn-ignored",
68
- "prettier --write",
69
- "prettier --check"
70
- ],
71
- "*.md": [
72
- "prettier --write",
73
- "prettier --check"
74
- ]
75
- },
76
- "publishAliases": [
77
- "gh-upload-log"
78
- ],
79
39
  "files": [
80
40
  "src",
81
41
  "README.md",