forked from WeblateOrg/weblate
-
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
build(deps): bump @sentry/browser from 6.19.7 to 7.21.1 in /scripts/yarn #263
Closed
dependabot
wants to merge
1
commit into
main
from
dependabot/npm_and_yarn/scripts/yarn/sentry/browser-7.21.1
Closed
build(deps): bump @sentry/browser from 6.19.7 to 7.21.1 in /scripts/yarn #263
dependabot
wants to merge
1
commit into
main
from
dependabot/npm_and_yarn/scripts/yarn/sentry/browser-7.21.1
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
Bumps [@sentry/browser](https://github.com/getsentry/sentry-javascript) from 6.19.7 to 7.21.1. - [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.19.7...7.21.1) --- updated-dependencies: - dependency-name: "@sentry/browser" dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Superseded by #268. |
nijel
added a commit
that referenced
this pull request
Aug 7, 2023
This allows to introduce component categorization in the future, see #263
nijel
added a commit
that referenced
this pull request
Aug 7, 2023
This allows to introduce component categorization in the future, see #263
nijel
added a commit
that referenced
this pull request
Aug 7, 2023
This allows to introduce component categorization in the future, see #263
nijel
added a commit
that referenced
this pull request
Aug 7, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix).
nijel
added a commit
that referenced
this pull request
Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix).
nijel
added a commit
that referenced
this pull request
Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix).
nijel
added a commit
that referenced
this pull request
Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix).
nijel
added a commit
that referenced
this pull request
Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix).
nijel
added a commit
that referenced
this pull request
Aug 8, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). TODO: Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place. TODO: Changed object filtering for changes. - last_changes_url should have just path - parsing should use path style parsing
nijel
added a commit
that referenced
this pull request
Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). TODO: Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place. TODO: Changed object filtering for changes. - last_changes_url should have just path - parsing should use path style parsing
nijel
added a commit
that referenced
this pull request
Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place.
nijel
added a commit
that referenced
this pull request
Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place.
nijel
added a commit
that referenced
this pull request
Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place.
nijel
added a commit
that referenced
this pull request
Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place.
nijel
added a commit
that referenced
this pull request
Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place.
nijel
added a commit
that referenced
this pull request
Aug 9, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place.
nijel
added a commit
that referenced
this pull request
Aug 10, 2023
Avoid using fixed structure for object URLs. All objects are now referected as path with possibly variable number of elements. This allows to introduce component categorization in the future, see #263. This change also forced change of some URLs which would no longer be distinguishable (anything under component can no longer have variable suffix). Changed widgets URLs to better fit in the new structure. Redirects for old ones are in place.
nijel
added a commit
that referenced
this pull request
Aug 11, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation
nijel
added a commit
that referenced
this pull request
Aug 11, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation
nijel
added a commit
that referenced
this pull request
Aug 11, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - document adjusted API lookups (category in component, %2F)
nijel
added a commit
that referenced
this pull request
Aug 11, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - document adjusted API lookups (category in component, %2F)
nijel
added a commit
that referenced
this pull request
Aug 12, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - document adjusted API lookups (category in component, %2F)
nijel
added a commit
that referenced
this pull request
Aug 12, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - document adjusted API lookups (category in component, %2F)
nijel
added a commit
that referenced
this pull request
Aug 12, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - document adjusted API lookups (category in component, %2F)
nijel
added a commit
that referenced
this pull request
Aug 14, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - tests - documentation
nijel
added a commit
that referenced
this pull request
Aug 15, 2023
This will make projectlanguge and category work consistently at all levels. Issue #263
nijel
added a commit
that referenced
this pull request
Aug 16, 2023
This will make projectlanguge and category work consistently at all levels. Issue #263
nijel
added a commit
that referenced
this pull request
Aug 16, 2023
This will make projectlanguge and category work consistently at all levels. Issue #263
nijel
added a commit
that referenced
this pull request
Aug 16, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - tests - documentation
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add category view template - add UI to: - add a category - delete a category - move component between categories - add documentation - add tests - add API - tests - documentation
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move a category to another - move component between categories - add documentation - API - user - add tests - API - create / update / delete - UI - add - browse - delete - move component to a category - rename category - move category
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add UI to: - add a category - delete a category - move a category to another - move component between categories - add documentation - API - user - add tests - API - create / update / delete - UI - add - browse - delete - move component to a category - rename category - move category
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add documentation - API - user - add tests - API - create / update / delete - UI - add - browse - delete - move component to a category - move a category to another - rename category - move category to another project - verify repositories moved together with category
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add documentation - API - user - add tests - API - create / update / delete - UI - add - browse - delete - move component to a category - move a category to another - rename category - move category to another project - verify repositories moved together with category
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add documentation - API - user - add tests - API - create / update / delete - UI - add - browse - delete - move component to a category - move a category to another - rename category - move category to another project - verify repositories moved together with category
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add documentation - user - add tests - UI - add - browse - delete - move component to a category - move a category to another - rename category - move category to another project - verify repositories moved together with category
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add tests - UI - delete - move a category to another - move category to another project
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263 TODO: - add tests - UI - move category to another project
nijel
added a commit
that referenced
this pull request
Aug 23, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263
nijel
added a commit
that referenced
this pull request
Aug 24, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263
nijel
added a commit
that referenced
this pull request
Aug 24, 2023
- add model for storing categories - browsing of project categories - support maximal depth of 3 categories rigth now Fixes #263
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/browser from 6.19.7 to 7.21.1.
Release notes
Sourced from
@sentry/browser
's releases.... (truncated)
Changelog
Sourced from
@sentry/browser
's changelog.... (truncated)
Commits
6866161
release: 7.21.13bd8da1
meta: Update changelog for 7.21.1 (#6268)b35e3d7
fix(nextjs): Stop excludingwithSentryConfig
from serverless bundles (#6267)99864fa
Merge branch 'release/7.21.0'90e53c3
release: 7.21.03fbf2a2
chore(otel): Update installation instructions (#6262)3d9f0fd
fix(nextjs): Exclude build-time files from page dependency manifests (#6058)4ffeedd
meta: Update changelog for 7.21.0 (#6260)3fe5f7a
fix(core): Only generate eventIds in client (#6247)72c6855
fix(express): Support multiple routers with common paths. (#6253)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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)