Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: quicknode/cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
Loading
...
head repository: quicknode/cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: package_management
Choose a head ref
Loading
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 7 files changed
  • 1 contributor

Commits on Jun 5, 2026

  1. Add release-update-homebrew-tap recipe for manual formula pushes

    cargo-dist generates qn.rb as a release artifact regardless of whether
    the "homebrew" entry is in publish-jobs. Until we have a
    HOMEBREW_TAP_TOKEN secret (which needs a Quicknode-owned PAT we don't
    yet have), the auto-push step stays disabled and this Justfile recipe
    lets a maintainer manually sync the formula to a local clone of
    quicknode/homebrew-tap.
    
    Usage:
    
      just release-update-homebrew-tap 0.1.0 ~/qn/homebrew-tap
    
    The recipe downloads qn.rb from the release, drops it at
    Formula/qn.rb in the tap clone, commits with a clean message, and
    prints the git push command (it does not push automatically — the
    maintainer reviews and pushes themselves).
    
    When HOMEBREW_TAP_TOKEN exists we'll add "homebrew" back to
    publish-jobs in dist-workspace.toml, the cargo-dist publish-homebrew
    job takes over, and this recipe becomes a fallback for manual recovery.
    johnpmitsch committed Jun 5, 2026
    Configuration menu
    Copy the full SHA
    6938ecb View commit details
    Browse the repository at this point in the history
  2. Document Homebrew + crates.io install paths in README

    The Quicknode tap at quicknode/homebrew-tap is populated with the v0.1.0
    formula (via release-update-homebrew-tap), so `brew install
    quicknode/tap/qn` works for anyone with access to the tap repo. Also
    add the crates.io path and fix the source-build remote (which still
    pointed at the never-created quicknode/qn instead of quicknode/cli).
    
    Drop the trailing "after pushing, paste this README snippet" hint from
    the release-update-homebrew-tap recipe — the README is now updated and
    the hint would just rot.
    johnpmitsch committed Jun 5, 2026
    Configuration menu
    Copy the full SHA
    e0f8c7e View commit details
    Browse the repository at this point in the history
  3. Package .deb files on release; sync permissions config with main

    Adds Debian package builds to the cargo-dist release pipeline:
    
    * [package.metadata.deb] in Cargo.toml configures cargo-deb to produce
      qn_X.Y.Z_<arch>.deb files (using the binary name in the filename,
      not the crate name).
    * .github/workflows/publish-deb.yml is a reusable workflow that, per
      arch (amd64/arm64), downloads the prebuilt linux-gnu archive from
      the GitHub release, stages the binary where cargo-deb expects it,
      packages with --no-build --no-strip, and uploads the .deb back to
      the release as an asset.
    * dist-workspace.toml gets ./publish-deb in publish-jobs and
      contents: write in github-custom-job-permissions (needed for `gh
      release upload`).
    
    Hosted apt repo (aptly/reprepro + GPG signing) is out of scope for v1.
    Users install via `dpkg -i ./qn_X.Y.Z_amd64.deb` or `apt install
    ./qn_X.Y.Z_amd64.deb` after downloading from the release page.
    
    Also brings this branch's publish-crates.yml and publish-docker.yml
    in line with the post-v0.1.0 fixes that landed on main:
    
    * publish-crates.yml gains `permissions: contents: read` so its
      reusable-workflow GITHUB_TOKEN can actually checkout this internal
      repo (without it, actions/checkout gets a 404).
    * publish-docker.yml drops `attestations: write` from its top-level
      permissions — that grant exceeded what the caller offered and was
      the original cause of the v0.1.0 startup_failure.
    * The release.yml regeneration also drops the homebrew publish job
      (no HOMEBREW_TAP_TOKEN yet — we publish manually via
      `just release-update-homebrew-tap`).
    
    Validated locally: cargo deb produced a structurally valid .deb with
    the right control metadata and /usr/bin/qn + /usr/share/doc/qn/ layout.
    johnpmitsch committed Jun 5, 2026
    Configuration menu
    Copy the full SHA
    3a0c2c4 View commit details
    Browse the repository at this point in the history
  4. Merge remote-tracking branch 'origin/main' into package_management

    # Conflicts:
    #	.github/workflows/publish-docker.yml
    #	.github/workflows/release.yml
    #	README.md
    #	dist-workspace.toml
    johnpmitsch committed Jun 5, 2026
    Configuration menu
    Copy the full SHA
    e502a58 View commit details
    Browse the repository at this point in the history
Loading
Morty Proxy This is a proxified and sanitized view of the page, visit original site.