mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[PR #1317] [CLOSED] Bump intl-messageformat from 9.13.0 to 10.2.5 #1856
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1856
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/floccusaddon/floccus/pull/1317
Author: @dependabot[bot]
Created: 1/8/2023
Status: ❌ Closed
Base:
develop← Head:dependabot/npm_and_yarn/intl-messageformat-10.2.5📝 Commits (1)
e8192c9Bump intl-messageformat from 9.13.0 to 10.2.5📊 Changes
2 files changed (+34 additions, -34 deletions)
View changed files
📝
package-lock.json(+33 -33)📝
package.json(+1 -1)📄 Description
Bumps intl-messageformat from 9.13.0 to 10.2.5.
Release notes
Sourced from intl-messageformat's releases.
Commits
2e261d3build: publishe6f7ea2chore: relax tslib semver constraint (#3924)8203ebfchore: revert the addition of missing publish steps and add more clarifications80ee32bbuild: publishe764507chore: add missing steps to the publish workflowfec8de5chore: rename swc-plugin-formatjs to@formatjs/swc-plugin-experimentalbb27372build: publish1cfdcf2chore: mention GH_TOKEN setup in the publish workflow doc (#3923)2887c98chore: add@formatjs/swc-plugin-experimentalto the published packages (#3922)051527bfix(@formatjs/intl): update monorepo to use TypeScript 4.9 and actually fix t...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 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)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.