mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[PR #672] [MERGED] Bump chrome-webstore-upload from 0.2.2 to 0.4.2 #1702
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#1702
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/672
Author: @dependabot-preview[bot]
Created: 10/6/2020
Status: ✅ Merged
Merged: 10/14/2020
Merged by: @marcelklehr
Base:
develop← Head:dependabot/npm_and_yarn/chrome-webstore-upload-0.4.2📝 Commits (1)
a6b88a0Bump chrome-webstore-upload from 0.2.2 to 0.4.2📊 Changes
2 files changed (+231 additions, -5 deletions)
View changed files
📝
package-lock.json(+230 -4)📝
package.json(+1 -1)📄 Description
Bumps chrome-webstore-upload from 0.2.2 to 0.4.2.
Release notes
Sourced from chrome-webstore-upload's releases.
Commits
3f24a600.4.20cae205Avoid using faulty got@11.6 dependency43b420e0.4.0d4e6ebbLint and modernize (#40)07c47a7Update got module (#39)39d7a5d0.3.1b2f1018Revert faulty dependency updatesad2f0130.3.09be2aadUpdate Got to latest version444e335Mention "Desktop app" type in API key guideMaintainer changes
This version was pushed to npm by fregante, a new releaser for chrome-webstore-upload since your current version.
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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.