gh-upload-file 0.0.0-stage → 0.13.0

package/CHANGELOG.md

@@ -0,0 +1,253 @@
+# gh-upload-log
+
+## 0.13.0
+
+### Minor Changes
+
+- 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.
+
+  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.
+
+  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`.
+
+  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.
+
+## 0.12.1
+
+### Patch Changes
+
+- b30b770: Track the published compatibility package in the README badge, explain renamed-package availability, and add actionable npm authorization diagnostics.
+
+## 0.12.0
+
+### Minor Changes
+
+- 3b926b7: Publish the universal package as `gh-upload-file`: npm refuses `gh-upload` as too similar to `rc-upload`. The `gh-upload` command is unchanged and `gh-upload-file` is added as a command.
+
+## 0.11.0
+
+### Minor Changes
+
+- b86bb49: Publish gh-upload alongside gh-upload-log with both command names and an uploadFile API alias. Automatically archive binary files with streaming gzip and split oversized archives into parts of at most 100 MB, while retaining readable text uploads, retries and resume support. Verify publication of every package name with uncached npm registry checks before creating a release.
+
+## 0.10.1
+
+### Patch Changes
+
+- de23ee4: Give real Git integration tests explicit Windows-sized timeouts and bounded subprocess diagnostics so slow runners do not block releases at Bun's default five-second limit.
+
+## 0.10.0
+
+### Minor Changes
+
+- 722cc83: Add explicit existing repository and branch targets for installation-token uploads without querying the authenticated user or creating repositories. Keep repository reads scoped to the selected branch and distinguish permanent Gist permission failures from retryable rate limits.
+
+## 0.9.3
+
+### Patch Changes
+
+- ea2dc72: Retry transient shared-repository push failures with exponential backoff and fetch/rebase recovery. Commit and push each log chunk separately, and resume incomplete uploads without treating the first chunk as a complete log. Add `--chunk-size` / `GH_UPLOAD_LOG_CHUNK_SIZE` and the library `chunkSize` option. Split chunks on line boundaries where possible and preserve UTF-8 characters when a line exceeds the byte limit.
+
+## 0.9.2
+
+### Patch Changes
+
+- 1b31255: Fail the release workflow when release-note formatting commands fail, and run both formatting helpers with Bun and locked dependencies.
+
+## 0.9.1
+
+### Patch Changes
+
+- 770cea8: Ship the existing relative-path upload fix to npm by repairing trusted publishing, reject failed publish commands instead of creating false-success GitHub releases, and report the installed package version from the CLI.
+
+## 0.9.0
+
+### Minor Changes
+
+- a00463b: Upload a log again when its content changed, even if the same path was uploaded before (#38).
+
+  Repository-mode uploads are now content addressed: logs are stored as
+  `<normalized-directory>/<content-hash>/<file-name>.log.txt` instead of
+  `log-<flattened-path>/<flattened-path>.log.txt`. A changed file gets a new hash
+  folder and is uploaded again, identical content is deduplicated and links to the
+  file that actually exists, and the path is no longer duplicated in the folder and
+  file names.
+  - Deduplication now checks that the expected file exists in the folder, so a
+    partial upload is retried instead of being reported as complete.
+  - New `--gist-limit` / `GH_UPLOAD_LOG_GIST_LIMIT` option to configure the gist
+    size threshold (clamped to GitHub's documented 100MB per gist file).
+  - Gist creation retries on transient `502`/`503`/`504` responses instead of failing.
+  - New `--check-raw-url` / `GH_UPLOAD_LOG_CHECK_RAW_URL` option verifies that the
+    reported raw URL is reachable, with a hint about private-repository token expiry.
+  - Verbose mode reports the content hash, stored file name and deduplication decision.
+  - `self-test` cleanup refuses to delete the shared `private-logs`/`public-logs`
+    repositories.
+
+## 0.8.3
+
+### Patch Changes
+
+- c6cc736: Accept every log file path form (bare relative, `./`, `../`, `~/`, absolute) by resolving paths to absolute before use, run git commands with command-stream's `cwd` option instead of a `cd` prefix that changed the process working directory, and initialize temporary repositories with `git -c init.defaultBranch=<branch> init -q` so the "Using 'master' as the name for the initial branch" hint and other command noise are no longer printed.
+
+## 0.8.2
+
+### Patch Changes
+
+- 5d82718: Use `.log.txt` names for uploaded log files so raw gist and repository links open as text in browsers.
+
+## 0.8.1
+
+### Patch Changes
+
+- 647ab73: Route repository fallbacks through shared log repositories by default.
+
+## 0.8.0
+
+### Minor Changes
+
+- 4c94056: Default large repository uploads to the shared `private-logs` /
+  `public-logs` repositories, skip duplicate large-log uploads that already
+  exist there, and add CLI/library configuration to keep the legacy dedicated
+  repository flow when needed. Also update `lino-arguments` to `0.3.0`.
+
+## 0.7.1
+
+### Patch Changes
+
+- 4c2044e: Handle repository-create exit failures correctly and retry with a unique
+  repository name when the generated name already exists.
+
+## 0.7.0
+
+### Minor Changes
+
+- 940281d: Handle ENOSPC (no space left on device) errors gracefully with actionable error messages, disk cleanup suggestions, and smart fallback prevention. Gist uploads can work without extra disk space; the tool now suggests --only-gist when appropriate.
+
+## 0.6.1
+
+### Patch Changes
+
+- 524dc7e: Fail early with a clean error message when the specified file does not exist, avoiding unnecessary output like the upload status line before the error.
+
+## 0.6.0
+
+### Minor Changes
+
+- 05f977a: Add direct raw file URL support for single-file uploads
+
+  When uploading a single log file (not split into chunks), the tool now displays a direct link to the raw file content in addition to the repository/gist URL.
+
+  For gists:
+  - Returns the permanent `raw_url` from the GitHub API
+  - This URL is accessible without authentication (even for secret gists)
+
+  For repositories:
+  - Returns the `download_url` from the GitHub API
+  - For private repositories, includes a token that enables unauthenticated access
+  - Displays a warning that the token expires in ~10 minutes for private repos
+
+  Example output:
+
+  ```
+  ✅ Gist created (🔒 private)
+  🔗 https://gist.github.com/user/abc123
+  📄 https://gist.githubusercontent.com/user/abc123/raw/hash/file.log
+  ```
+
+  This enhancement addresses issue #21 and makes it easier to share direct links to uploaded log files.
+
+## 0.5.0
+
+### Minor Changes
+
+- 428588e: Fix gist upload failing with HTTP 502 for large files
+  - Lower gist threshold from 100MB to 25MB to match GitHub's web interface limit and avoid HTTP 502 errors
+  - Add validation to detect failed gist creation (empty URL in stdout)
+  - Add automatic fallback from gist to repository mode when gist upload fails
+  - Add --test and --quick CLI flags for self-testing upload functionality
+  - Add test file generator script for different file sizes
+  - Update unit tests for new behavior
+
+## 0.4.1
+
+### Patch Changes
+
+- 456226d: Add npm version badge to README.md for better package visibility
+
+## 0.4.0
+
+### Minor Changes
+
+- 32150a1: Make output more user friendly with cleaner, shorter format and emojis
+  - Reduced duplicate information (file size, URL were shown multiple times)
+  - Added colorful emojis for visual clarity: ⏳ (uploading), ✅ (success), 🔍 (dry run), 🔒 (private), 🌐 (public), 🔗 (URL)
+  - Moved verbose details (strategy, mode, file name) to --verbose mode only
+  - Output is now short and minimalistic by default while preserving all important information (size, visibility, URL)
+
+## 0.3.1
+
+### Patch Changes
+
+- 9719c35: fix: Gist URL capture and human-readable file size display
+  - Fix gist URL not being captured due to empty string interpolation in command-stream template literal
+  - Add formatFileSize() function for human-readable file sizes (e.g., "1.90 KB" instead of "0.00 MB")
+  - Improve CLI output with better formatting and file info display before upload
+  - Add comprehensive tests for formatFileSize function
+
+## 0.3.0
+
+### Minor Changes
+
+- 2cc28d3: feat: Make repository Bun-only
+  - Updated README.md to use Bun instead of Node.js/npm/Deno
+  - Changed all shebangs from `#!/usr/bin/env node` to `#!/usr/bin/env bun`
+  - Updated package.json scripts to use Bun commands
+  - Updated CI workflows to only run Bun tests (3 OS matrix: Ubuntu, macOS, Windows)
+  - Removed deno.json configuration file
+  - Changed engine requirement from Node.js to Bun ≥1.0.0
+
+## 0.2.0
+
+### Minor Changes
+
+- 76ccd16: Complete template feature alignment with manual release support and enhanced CI/CD
+
+  This release implements ALL missing features from the js-ai-driven-development-pipeline-template repository:
+
+  **Manual Release Support**:
+  - **Instant releases**: Trigger immediate version bumps and npm publishing via GitHub Actions UI
+  - **Changeset PR mode**: Create pull requests with changesets for review before release
+  - **workflow_dispatch trigger**: Supports patch, minor, and major version bumps with optional descriptions
+
+  **Enhanced CI/CD**:
+  - **PR-scoped validation**: Only validates changesets added by the current PR using git diff, preventing failures when other PRs merge first
+  - **Multiple changeset merging**: Automatically merges multiple changesets during release with highest bump type selection and chronological description preservation
+  - **Modular release scripts**: Migrated to modular architecture using lino-arguments, command-stream, and use-m
+  - **OIDC trusted publishing**: Secure npm publishing without stored tokens
+
+  **New Scripts**:
+  - `version-and-commit.mjs` - Unified version bumping and git commits
+  - `publish-to-npm.mjs` - OIDC-enabled npm publishing
+  - `create-github-release.mjs` - Automated GitHub release creation
+  - `format-github-release.mjs` - Release note formatting with PR detection
+  - `create-manual-changeset.mjs` - Manual changeset file generation
+  - `setup-npm.mjs` - npm OIDC setup for trusted publishing
+  - `instant-version-bump.mjs` - Fast-track version bumps without changesets
+
+  These improvements provide complete feature parity with the template repository and enable flexible release workflows.
+
+## 0.1.1
+
+### Patch Changes
+
+- ffde303: **Bug Fix**: Fixed CLI showing "Arguments public and private are mutually exclusive" error on every invocation
+
+  **Root Cause**: The `--public` and `--private` options had default values which caused yargs' `.conflicts()` method to always trigger, preventing the CLI from working at all.
+
+  **Solution**: Removed default values from conflicting CLI options (`--public`/`--private` and `--only-gist`/`--only-repository`). Default behavior is now handled in application code.
+
+  **Impact**: This critical bug prevented the CLI from working at all when installed via npm or bun. Users can now use the tool as intended.
+
+  **Testing**: Added comprehensive integration tests to verify the fix and prevent regression.
+
+  Fixes #6

package/LICENSE

@@ -0,0 +1,24 @@
+This is free and unencumbered software released into the public domain.
+
+Anyone is free to copy, modify, publish, use, compile, sell, or
+distribute this software, either in source code form or as a compiled
+binary, for any purpose, commercial or non-commercial, and by any
+means.
+
+In jurisdictions that recognize copyright laws, the author or authors
+of this software dedicate any and all copyright interest in the
+software to the public domain. We make this dedication for the benefit
+of the public at large and to the detriment of our heirs and
+successors. We intend this dedication to be an overt act of
+relinquishment in perpetuity of all present and future rights to this
+software under copyright law.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
+OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.
+
+For more information, please refer to <https://unlicense.org>