GabeDuarteM/semantic-release-chrome

Issues

• Fails when manifest.json contains comments

  #115 opened 3 months ago by melink14
  0

• No way to update the non-dist version of manifest.json

  #81 opened 4 years ago by melink14
  1

• Question: Do Refresh Tokens Expire? If so, how to handle that?

  #114 opened 8 months ago by Jgordon-pencilwrench
  0

• Allow publishing of pre-release version

  #111 opened a year ago by nate-pratt
  5

• Multiple release branches/channels

  #24 opened 2 years ago by craigsketchley
  3

• Runtime error: PKG_INVALID_ZIP Invalid package.

  #89 opened 3 years ago by dmitrif
  3

• Unable to obtain refresh token as suggested in Authentication.md

  #105 opened 2 years ago by nikicat
  2

• Dependency Dashboard

  #92 opened 3 years ago by renovate
  0

• Question: Semantic versioning without publish

  #103 opened 2 years ago by sbahir
  1

• FR: Define some common lodash templates for asset naming

  #82 opened 2 years ago by melink14
  2

• Provide better error message on 400 Bad Request

  #69 opened 2 years ago by felixfbecker
  2

• Update to the latest version of chrome-webstore-upload to avoid vulnerability in got package

  #94 opened 2 years ago by melink14
  1

• [Feature] Add new target 'draft', which uploads but does not publish

  #60 opened 2 years ago by dword-design
  2

• Skip publish

  #90 opened 2 years ago by imsergiobernal
  1

• HTTP Error 400 when Publishing

  #7 opened 6 years ago by keplersj
  2

• PUBLISHED_WITH_FRICTION_WARNING makes semantic-release-chrome fail

  #46 opened 5 years ago by exKAZUu
  1

• Release failing but extension got updated

  #41 opened 5 years ago by sebbi08
  4

• The automated release is failing 🚨

  #1 opened 6 years ago by GabeDuarteM
  0