Closed JuliaTagBot closed 3 years ago
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24800
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/36735
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/39974
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
@quinnj do you happen to know why this is happening? I believe it started after MemPool was migrated to JuliaData.
Yeah, looks like we were missing the deploy keys; I've updated them now
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/42998
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/46747
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/46855
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/47096
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63439
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63586
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/64041
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88199
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88996
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/95519
Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.
This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your
TagBot.yml
to include issue comment triggers. Please see this post on Discourse for instructions and more details.