-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version Packages #298
Version Packages #298
Conversation
dbb2368
to
722dab5
Compare
a0bc90a
to
b139b70
Compare
c16f49d
to
4884081
Compare
968048e
to
384bfd3
Compare
85963a0
to
1483142
Compare
1483142
to
99a6b0f
Compare
8def5d9
to
74efa69
Compare
7458839
to
f79b61d
Compare
d41bc69
to
1197006
Compare
ff702e8
to
d1677f9
Compare
@SimenB minor inconvenience, but when your fork opens this PR it adds noise to the PRs that it mentions. Can you disable the action in the fork (or take some other measure to prevent it)? Example: |
d1677f9
to
f4d9e34
Compare
Ah, sorry! Disabled actions now |
@trevor-scheer you can also tweak your action to only run in your own repo. I would assume this is an issue with all forks? |
@SimenB thats helpful, TIL! Definitely going to do that. Thanks for the tip. |
Our release GH action currently runs in forks as well. This is made particularly obvious by the fact that the action itself opens a PR which references a bunch of other PRs (so we get additional noise per fork on all of our closed PRs). Ref: SimenB#298 (comment) This conditional prevents the action from running anywhere but this repo.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@apollo/server-integration-testsuite@4.3.3
Patch Changes
9de18b34c
]:@apollo/server@4.3.3
Patch Changes
9de18b34c
Thanks @trevor-scheer! - Unpinnode-abort-controller
and update to latest unbreaking patch