Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[extension-browser] Auto-sign and increment extension versions #2497

Closed
4 tasks
antross opened this issue May 23, 2019 · 0 comments
Closed
4 tasks

[extension-browser] Auto-sign and increment extension versions #2497

antross opened this issue May 23, 2019 · 0 comments
Assignees
@molant
Milestone
1906-1

Comments

@antross
Copy link
Member

antross commented May 23, 2019 •
edited by molant

  • Auto-increase the version (we will start with 0.0.1 for now until we go out of beta)
  • Generate bundles for each store
  • Sign them automatically (web-ext for Firefox, need to look into Chrome)
  • Use the same guid for Firefox so we don't publish it multiple times (is there something to do for Chrome?)

Is there something else I'm forgetting @antross?

Originally posted by @molant in #1641 (comment)
@antross antross added this to the 1906-1 milestone May 23, 2019
molant added a commit to molant/hint that referenced this issue May 24, 2019
@molant
Chore: Util to bump package and manifest version on release
c04d2cb 
Publishing from the CLI is not an easy task and has some limitations:

* Chrome: Need to create an OAuth app and then token expires after 40'.
  There are some packages that facilitate this but several environment
  variables will have to be set in the user's machine.
* Firefox: `web-ext` does not report the right status when updating a
  published extension.

After discussion the agreement was to open a browser with the Chrome and
Firefox store opened to manually upload the bundle file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#2497
Ref: mozilla/web-ext#804 (comment)
molant added a commit to molant/hint that referenced this issue May 24, 2019
@molant
Chore: Util to bump package and manifest version on release
866a395 
Publishing from the CLI is not an easy task and has some limitations:

* Chrome: Need to create an OAuth app and then token expires after 40'.
  There are some packages that facilitate this but several environment
  variables will have to be set in the user's machine.
* Firefox: `web-ext` does not report the right status when updating a
  published extension.

After discussion the agreement was to open a browser with the Chrome and
Firefox store opened to manually upload the bundle file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#2497
Ref: mozilla/web-ext#804 (comment)
molant added a commit to molant/hint that referenced this issue May 24, 2019
@molant
Chore: Util to bump package and manifest version on release
8faa94b 
Publishing from the CLI is not an easy task and has some limitations:

* Chrome: Need to create an OAuth app and then token expires after 40'.
  There are some packages that facilitate this but several environment
  variables will have to be set in the user's machine.
* Firefox: `web-ext` does not report the right status when updating a
  published extension.

After discussion the agreement was to open a browser with the Chrome and
Firefox store opened to manually upload the bundle file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#2497
Ref: mozilla/web-ext#804 (comment)
@molant molant mentioned this issue May 24, 2019
Closed
2 tasks
molant added a commit to molant/hint that referenced this issue May 24, 2019
@molant
Chore: Util to bump package and manifest version on release
f851f56 
Publishing from the CLI is not an easy task and has some limitations:

* Chrome: Need to create an OAuth app and then token expires after 40'.
  There are some packages that facilitate this but several environment
  variables will have to be set in the user's machine.
* Firefox: `web-ext` does not report the right status when updating a
  published extension.

After discussion the agreement was to open a browser with the Chrome and
Firefox store opened to manually upload the bundle file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#2497
Ref: mozilla/web-ext#804 (comment)
molant added a commit to molant/hint that referenced this issue May 30, 2019
@molant
Chore: Util to bump package and manifest version on release
5f07efb 
Publishing from the CLI is not an easy task and has some limitations:

* Chrome: Need to create an OAuth app and then token expires after 40'.
  There are some packages that facilitate this but several environment
  variables will have to be set in the user's machine.
* Firefox: `web-ext` does not report the right status when updating a
  published extension.

After discussion the agreement was to open a browser with the Chrome and
Firefox store opened to manually upload the bundle file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fix webhintio#2497
Ref: mozilla/web-ext#804 (comment)
@molant molant closed this as completed in 20a9df7 May 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@molant molant

Labels
None yet
Projects
None yet
Milestone
1906-1
Development

Successfully merging a pull request may close this issue.

Chore: Util to bump package and manifest version on release molant/hint
2 participants
@molant @antross