This repository has been archived by the owner on Jun 11, 2021. It is now read-only.
chore(deps): bump @sentry/node from 6.2.1 to 6.2.3 in /accounter/connector #692
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
@dependabot rebase |
auto-merge was automatically disabled
March 24, 2021 10:39
Head branch was pushed to by a user without write access
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
from
8d1581a to
670f6bf
Compare
|
@dependabot rebase |
auto-merge was automatically disabled
March 24, 2021 11:45
Head branch was pushed to by a user without write access
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
from
670f6bf to
fa796b0
Compare
|
@dependabot rebase |
auto-merge was automatically disabled
March 24, 2021 12:02
Head branch was pushed to by a user without write access
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
from
fa796b0 to
b03553a
Compare
|
@dependabot rebase |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
from
b03553a to
1783cda
Compare
Terraform Plan 📖Show Provider Plandigitalocean_container_registry.accounter: Refreshing state... [id=accounter]
digitalocean_database_cluster.database: Refreshing state... [id=455151ed-8a33-4a2b-bf3c-56c189779760]
digitalocean_kubernetes_cluster.accounter: Refreshing state... [id=d285b7e9-271a-49da-b0a8-21b81f05cd20]
digitalocean_database_firewall.database-fw: Refreshing state... [id=455151ed-8a33-4a2b-bf3c-56c189779760-20210204084818819800000001]
No changes. Infrastructure is up-to-date.
This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.Show Cluster Planmodule.loadbalancer.helm_release.ingress-nginx: Refreshing state... [id=ingress-nginx]
digitalocean_spaces_bucket.assets: Refreshing state... [id=accounter-assets-bucket]
module.loadbalancer.kubernetes_service.loadbalancer: Refreshing state... [id=default/loadbalancer]
module.web.kubernetes_service.web: Refreshing state... [id=default/web]
module.loadbalancer.kubernetes_namespace.cert-manager: Refreshing state... [id=cert-manager]
module.connector.kubernetes_secret.slack-credentials: Refreshing state... [id=default/slack-credentials]
module.connector.kubernetes_secret.zoom-workspace-credentials: Refreshing state... [id=default/zoom-workspace-credentials]
module.connector.kubernetes_service.connector: Refreshing state... [id=default/connector]
module.server.kubernetes_secret.secret-key: Refreshing state... [id=default/secret-key]
module.server.kubernetes_service.server: Refreshing state... [id=default/server]
module.connector.kubernetes_secret.google-workspace-credentials: Refreshing state... [id=default/google-workspace-credentials]
module.connector.kubernetes_secret.token-encryption: Refreshing state... [id=default/token-encryption]
module.connector.kubernetes_secret.github-credentials: Refreshing state... [id=default/github-credentials]
digitalocean_container_registry_docker_credentials.registry: Refreshing state... [id=accounter]
module.server.kubernetes_secret.sendgrid-api-key: Refreshing state... [id=default/sendgrid-api-key]
module.server.kubernetes_secret.database-credentials: Refreshing state... [id=default/database-credentials]
module.loadbalancer.helm_release.cert-manager: Refreshing state... [id=cert-manager]
module.server.kubernetes_secret.s3-credentials: Refreshing state... [id=default/s3-credentials]
kubernetes_secret.registry-accounter: Refreshing state... [id=default/registry-accounter]
module.server.kubernetes_deployment.server: Refreshing state... [id=default/server]
module.connector.kubernetes_deployment.connector: Refreshing state... [id=default/connector]
module.loadbalancer.kubernetes_deployment.loadbalancer: Refreshing state... [id=default/loadbalancer]
module.web.kubernetes_deployment.web: Refreshing state... [id=default/web]
module.loadbalancer.kubernetes_manifest.cert-issuer: Refreshing state...
module.loadbalancer.kubernetes_ingress.loadbalancer: Refreshing state... [id=default/loadbalancer]
No changes. Infrastructure is up-to-date.
This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed. |
auto-merge was automatically disabled
March 24, 2021 14:54
Head branch was pushed to by a user without write access
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
3 times, most recently
from
65e4a1a to
7adbe8a
Compare
|
@dependabot rebase |
auto-merge was automatically disabled
March 25, 2021 13:11
Head branch was pushed to by a user without write access
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
from
7adbe8a to
3359dd9
Compare
auto-merge was automatically disabled
March 25, 2021 13:27
Head branch was pushed to by a user without write access
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
2 times, most recently
from
9776aa4 to
1c2e657
Compare
Bumps [@sentry/node](https://github.com/getsentry/sentry-javascript) from 6.2.1 to 6.2.3. - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/master/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@6.2.1...6.2.3) Signed-off-by: dependabot[bot] <[email protected]>
auto-merge was automatically disabled
March 25, 2021 13:57
Head branch was pushed to by a user without write access
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
from
1c2e657 to
8228c65
Compare
|
@dependabot merge |
dependabot
bot
deleted the
dependabot/npm_and_yarn/accounter/connector/sentry/node-6.2.3
branch
|
🎉 This PR is included in version 1.76.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps @sentry/node from 6.2.1 to 6.2.3.
Release notes
Sourced from
@sentry/node's releases.Changelog
Sourced from
@sentry/node's changelog.Commits
dbb243crelease: 6.2.3d2a032fmisc: 6.2.3 changelogcb66fa4VERCEL_GITHUB_COMMIT_SHA → VERCEL_GIT_COMMIT_SHA (#3337)57423eeMerge release/6.2.2 into master547a01erelease: 6.2.2a31ac41misc: 6.2.2 changelogf824c80fix: Normalized Event before caching. (#3305)02a8c59chore(deps): bump elliptic from 6.5.3 to 6.5.4 (#3315)97daa3bchore(deps): bump elliptic in /packages/node/test/manual/webpack-domain (#3320)0abfa10misc: Clarified description of browser SDK (#3322)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot will merge this PR once it's up-to-date and CI passes on it, as requested by @MoSattler.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)