Skip to content
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: chrisspiegl/pushnotice-node-api-client
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.3.4
Choose a base ref
...
head repository: chrisspiegl/pushnotice-node-api-client
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
  • 16 commits
  • 4 files changed
  • 1 contributor

Commits on Mar 16, 2025

  1. fix(devops): we should only publish to npm when the release has been … 

    …published
    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    3b38291 View commit details

  2. chore: release v0.3.5

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    0ce6c02 View commit details

  3. fix(devops): hopefully the action now triggers

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    e5addea View commit details

  4. chore: release v0.3.6

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    43deefa View commit details

  5. fix(devops): apparently using secrets.GITHUB_ACTION, it does not tr… 

    …igger followup workflows thus preventing the `on: release` to trigger. Combining the workflows into one.
    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    b807746 View commit details

  6. chore: release v0.3.7

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    5291891 View commit details

  7. fix(devops): for provenance we need id-token write access

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    8f5d3a2 View commit details

  8. chore: release v0.3.8

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    224e0cf View commit details

  9. fix(devops): need to have the correct url for provenance

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    7a5ba16 View commit details

  10. chore: release v0.3.9

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    2fa6149 View commit details

  11. fix(devops): need to have the correct url for provenance

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    0571758 View commit details

  12. chore: release v0.3.10

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    72d978e View commit details

  13. fix(devops): need to have the correct url for provenance (I forgot … 

    …that 8 years ago, I had a different user name on github).
    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    f6989b2 View commit details

  14. chore: release v0.3.10

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    ac89a74 View commit details

  15. chore: release v0.3.11

    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    73f8d66 View commit details

  16. fix(docs): add some reminders for how releasing a new version works s… 

    …o I may do it more swiftly in the future
    @chrisspiegl
    chrisspiegl committed Mar 16, 2025
    Copy the full SHA
    b87caa5 View commit details

This comparison is taking too long to generate.

Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.

You can try running this command locally to see the comparison on your machine:
git diff v0.3.4...main