Releases: codingnooob/blogbranch
Releases · codingnooob/blogbranch
Blog Link Analyzer v1.4.9
Blog Link Analyzer v1.4.9
Automated release with full pipeline testing
📦 Packages
- Chrome Web Store:
blog-link-analyzer-1.4.9.zip - Firefox Add-ons:
blog-link-analyzer-firefox-1.4.9.zip - Self-hosted:
blog-link-analyzer-1.4.9.crxandblog-link-analyzer-firefox-v1.4.9.xpi
✨ Features
- AI-powered blog content summarization
- Support for OpenAI, Anthropic, Ollama, and custom AI providers
- Cross-browser compatibility (Chrome & Firefox)
- Enhanced blog detection algorithms
🔧 Installation
Chrome Web Store
- Visit Chrome Web Store (link will be available after approval)
- Click 'Add to Chrome'
- Grant necessary permissions
Firefox Add-ons
- Visit Firefox Add-ons Developer Hub (link will be available after approval)
- Click 'Add to Firefox'
- Grant necessary permissions
Self-hosted
- Download the appropriate package for your browser
- Load the extension in developer mode
- Configure your AI provider settings
📋 Changelog
Automated release with full pipeline testing
Blog Link Analyzer v1.4.7 - Final File Path Fix
Final File Path Fix v1.4.7
Critical Fixes
- File Path Resolution: Use VERSION variable instead of tag substitution
- File Verification: Add verification step before deployment
- Simplified Workflow: Remove artifacts directory complexity
- Direct File References: Use direct file paths for deployment
Technical Changes
- VERSION Variable: Use ${VERSION} instead of tag substitution
- File Verification: Confirm files exist before deployment
- Deployment Paths: Direct file references to created artifacts
- Error Handling: Better debugging for missing files
Build Process
- Webpack Build: Creates popup.bundle.js and dist/ directory
- ZIP Creation: Creates blog-link-analyzer.zip and blog-link-analyzer-firefox.xpi
- Version-Specific: Creates blog-link-analyzer-${VERSION}.zip and blog-link-analyzer-firefox-${VERSION}.xpi
- File Verification: Confirms all files exist before deployment
Expected Outcome
- Chrome deployment should work with ZIP file available
- Firefox deployment should work with XPI file available
- No more 'File not found' errors
- End-to-end automated deployment pipeline functional
Error Resolution
- Chrome: Fixed 'File not found: blog-link-analyzer-v1.4.6.zip'
- Firefox: Fixed 'File not found: blog-link-analyzer-firefox-v1.4.6.xpi'
- File paths: Now use VERSION variable for consistent naming
This release should achieve 100% automated deployment success rate by resolving file path issues.
Blog Link Analyzer v1.4.6 - Missing Script Fix
Missing Script Fix v1.4.6
Critical Fix
- Missing Script: Added package:all-formats script to package.json
- Build Process: Now creates both Chrome and Firefox version-specific packages
- Workflow Integration: Fixed npm run command not found error
- Version Bump: Updated to 1.4.6 for testing
Technical Changes
- Package Script: Added package:all-formats for version-specific packaging
- Build Verification: Confirmed script creates required ZIP files
- Workflow Compatibility: Fixed npm run command in CI/CD pipeline
- Artifact Management: Clean version-specific file creation
Build Process
- Webpack Build: Creates popup.bundle.js and dist/ directory
- ZIP Creation: Creates blog-link-analyzer.zip and blog-link-analyzer-firefox.xpi
- Version Packaging: Creates version-specific copies for deployment
- Verification: Confirms all artifacts exist
Expected Outcome
- Chrome deployment should work with version-specific ZIP file
- Firefox deployment should work with version-specific XPI file
- No more 'file cannot be found' errors
- End-to-end automated deployment pipeline functional
This release resolves the missing script error that was preventing artifact creation.
Blog Link Analyzer v1.4.5 - ZIP Creation Fix
ZIP Creation Fix v1.4.5
Critical Fix
- ZIP Creation: Added archiver dependency and ZIP generation scripts
- Build Process: Now creates both Chrome ZIP and Firefox XPI files
- ES Module Syntax: Fixed CommonJS/ES module compatibility issues
- Artifact Verification: Added build output verification step
Technical Changes
- Dependencies: Added archiver for ZIP file creation
- Scripts: Created create-zip.js and create-firefox-zip.js
- Build Integration: Updated build scripts to include ZIP creation
- Workflow: Fixed build step dependencies and verification
- Module System: Converted to ES modules for compatibility
Build Process
- Webpack Build: Creates popup.bundle.js and dist/ directory
- ZIP Creation: Creates blog-link-analyzer.zip and blog-link-analyzer-firefox.xpi
- Verification: Confirms all artifacts exist before deployment
- Version-Specific: Creates version-specific copies for deployment
Expected Outcome
- Chrome deployment should work with ZIP file available
- Firefox deployment should work with XPI file available
- No more 'file cannot be found' errors
- End-to-end automated deployment pipeline functional
This release resolves the root cause: ZIP files were not being created during the build process.
Blog Link Analyzer v1.4.4 - Deployment Error Fixes
Deployment Error Fixes v1.4.4
Critical Fixes
- Chrome Glob Pattern: Fixed multiple files found error with specific filename
- Firefox Version Conflict: Bumped to 1.4.4 to avoid existing version 1.3.6
- Artifact Management: Added cleanup and version-specific naming
- Release Tag Integration: Use release tag for artifact naming
Technical Changes
- Artifact Cleanup: Remove old ZIP/XPI files before building
- Version-Specific Naming: blog-link-analyzer-{VERSION}.zip and blog-link-analyzer-firefox-{VERSION}.xpi
- Chrome Deployment: Use specific filename instead of glob pattern
- Firefox Deployment: Use specific filename with release tag
- Version Bump: 1.4.4 to avoid store conflicts
Expected Outcome
- Chrome deployment should work with specific filename (no multiple files)
- Firefox deployment should work with new version (no conflicts)
- Both stores should show successful uploads
- End-to-end automated deployment pipeline functional
Error Resolution
- Chrome: Fixed 'Multiple files found: blog-link-analyzer-*.zip'
- Firefox: Fixed 'Version 1.3.6 already exists'
- Artifacts: Clean, version-specific naming prevents conflicts
This release should achieve 100% automated deployment success rate for both browser stores.
Blog Link Analyzer v1.4.3 - Complete OAuth2 Authentication
Complete OAuth2 Authentication Test v1.4.3
Final Configuration
- All Chrome Secrets: CHROME_EXTENSION_ID, CHROME_CLIENT_ID, CHROME_CLIENT_SECRET, CHROME_REFRESH_TOKEN
- OAuth2 Authentication: Complete Chrome Web Store authentication flow
- Firefox Service Account: Continues working with JWT authentication
- Version Milestone: v1.4.3 represents complete authentication setup
Authentication Methods
- Chrome Web Store: OAuth2 with client credentials and refresh token
- Firefox Add-ons: Service account with JWT issuer/secret
- Parameter Validation: All action parameters verified correct
- Secret Configuration: All required secrets properly configured
Expected Outcome
- Chrome Web Store deployment should work with complete OAuth2 authentication
- Firefox Add-ons deployment continues working as before
- Both stores should show successful uploads and pending review
- End-to-end automated deployment pipeline fully functional
Technical Readiness
- Complete Chrome OAuth2 authentication configuration
- Firefox service account authentication working
- Secure configuration validation without secret exposure
- Comprehensive error handling and logging
- Version synchronization across all manifests
This release should achieve 100% automated deployment success rate for both browser stores.
Blog Link Analyzer v1.4.2 - Chrome OAuth2 Authentication
Chrome OAuth2 Authentication Test v1.4.2
Key Update
- Chrome Client ID Secret: CHROME_CLIENT_ID has been added to GitHub Secrets
- OAuth2 Authentication: Now using proper OAuth2 flow for Chrome Web Store
- Version Milestone: v1.4.2 marks authentication resolution attempt
- Firefox Continuity: Service account continues working for Firefox
Authentication Configuration
- Chrome Web Store: OAuth2 with client-id, client-secret, refresh-token
- Firefox Add-ons: Service account with JWT issuer/secret
- Parameter Validation: All Chrome action parameters verified correct
- Secret Configuration: All required secrets now available
Expected Outcome
- Chrome Web Store deployment should work with OAuth2 authentication
- Firefox Add-ons deployment continues working as before
- Both stores should show successful uploads
- End-to-end automated deployment pipeline functional
Technical Readiness
- All Chrome secrets now configured in GitHub Secrets
- Secure configuration validation in place
- Version synchronization across all manifests
- Comprehensive error handling and logging
This release tests the complete automated deployment pipeline with proper Chrome OAuth2 authentication.
Blog Link Analyzer v1.3.9 - Secure Configuration Validation
Secure Configuration Validation v1.3.9
Critical Fixes
- GitHub Actions Syntax: Fixed invalid length() function calls causing workflow failure
- Security Issue: Removed secret exposure from debug console (API tokens no longer visible)
- Safe Validation: Replaced secret inspection with configuration validation
- Best Practices: Follow security guidelines for secret handling
Technical Changes
- Remove unsupported length() function from workflow expressions
- Use boolean existence checks instead of secret value echoing
- Add bash script validation for Chrome secret configuration
- Maintain debugging capability without exposing sensitive data
- Clear success/failure messaging for configuration status
Expected Outcome
- No more GitHub Actions syntax errors
- Secure secret handling with no exposure in logs
- Clear indication of Chrome configuration status
- Chrome deployment should work with valid configuration
- Firefox deployment continues working as before
Security Improvements
- API tokens and secrets no longer visible in pipeline console
- Configuration validation without secret inspection
- Follows GitHub Actions security best practices
This release resolves both critical syntax error and security concern while maintaining debugging capability.
Blog Link Analyzer v1.3.8 - Chrome Secrets Debug
Chrome Secrets Debug v1.3.8
Key Findings from Documentation Review
- Chrome Action Parameters Verified: All parameter names are correct (client-id, client-secret, refresh-token, extension-id, zip-path)
- Firefox Success Confirms: Secret structure and workflow approach work correctly
- Issue Isolated: Chrome secrets specifically not accessible or empty
Debugging Enhancements
- Secret Existence Check: Shows if each Chrome secret exists
- Secret Length Check: Shows if secrets have actual values
- Comprehensive Logging: Detailed visibility into Chrome secret configuration
- Parameter Confirmation: All Chrome action parameters verified correct
Expected Debug Output
- CHROME_EXTENSION_ID existence and length
- CHROME_CLIENT_ID existence and length
- CHROME_CLIENT_SECRET existence and length
- CHROME_REFRESH_TOKEN existence and length
Next Steps
- If secrets show as existing but length 0: secrets are empty
- If secrets show as not existing: secret names incorrect
- If secrets show as existing with length: investigate other issues
This release will definitively identify the root cause of Chrome deployment failure.