-
Notifications
You must be signed in to change notification settings - Fork 0
Automate Chrome Web Store publishing #10
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
Conversation
- Create helper script to simplify getting GitHub refresh tokens - Update release workflow to use semantic versioning - Improve options page styling and token setup flow
Condensed README sections to be more skimmable - the accessibility and setup sections were way too verbose. Also updated storage capacity from 100 to 2000 items throughout docs and config since we increased that limit. Added note about NPM registry communication in privacy policy since that's not obvious to users.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR automates Chrome Web Store publishing and updates documentation and storage configurations. The changes introduce automated publishing via GitHub Actions when a release tag is pushed, increase the activity storage capacity from 100 to 2000 items, and streamline the README and privacy documentation to be more concise and scannable.
Key changes:
- Automated Chrome Web Store publishing in release workflow using OAuth credentials stored as GitHub secrets
- Increased MAX_ACTIVITIES_STORED from 100 to 2000 items with centralized configuration
- Condensed and simplified README, privacy policy, and contributing documentation
Reviewed Changes
Copilot reviewed 9 out of 11 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/release.yml |
Added Chrome Web Store publishing step with OAuth authentication |
shared/config.js |
Increased MAX_ACTIVITIES_STORED from 100 to 2000 |
shared/state-manager.js |
Updated to use STORAGE_CONFIG.MAX_ACTIVITIES_STORED constant |
options/options.js |
Added changelog footer with GitHub link |
options/options.css |
Added styling for changelog footer and link |
manifest.json |
Added CHANGELOG.md to web_accessible_resources, version bump to 1.0.2 |
package-lock.json |
Version bump to 1.0.2 |
README.md |
Streamlined documentation, added Chrome Web Store link, simplified sections |
PRIVACY.md |
Updated activity storage limit to 2000, added NPM registry section |
CONTRIBUTING.md |
Noted automated Chrome Web Store publishing |
.gitignore |
Added client_secret files and token script to ignore list |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
manifest.json
Outdated
| "web_accessible_resources": [ | ||
| { | ||
| "resources": ["CHANGELOG.md"], | ||
| "matches": ["<all_urls>"] | ||
| } | ||
| ] |
Copilot
AI
Nov 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The web_accessible_resources configuration exposes CHANGELOG.md to all URLs with matches: [\"<all_urls>\"]. This is overly permissive. Since the changelog is only accessed via chrome.runtime.getURL() in options.js (line 1053), web_accessible_resources is unnecessary. Extension resources accessed via chrome.runtime.getURL() don't require this declaration. Remove this section to avoid unnecessarily exposing extension files to web pages.
| "web_accessible_resources": [ | |
| { | |
| "resources": ["CHANGELOG.md"], | |
| "matches": ["<all_urls>"] | |
| } | |
| ] |
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 8 out of 10 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Changes
Chrome Web Store Publishing
Added automation to publish releases directly to the Chrome Web Store:
.github/workflows/release.ymlto automatically publish on releaseDocumentation Improvements
Tightened up README to be more skimmable:
Storage Updates
Testing
The Chrome Web Store publishing requires these GitHub secrets to be set:
CHROME_EXTENSION_IDCHROME_CLIENT_IDCHROME_CLIENT_SECRETCHROME_REFRESH_TOKEN