✅ Version updated to 2.0.4 in frontend/package.json
✅ CHANGELOG.md created with v2.0.4 entry
✅ RELEASE_NOTES_v2.0.4.md created
✅ Git tag v2.0.4 created and pushed
✅ Branch advisory-fix-1 ready for publishing
# Navigate to the frontend directory where package.json is located
cd frontend
# Verify the version is correct
cat package.json | grep '"version"'
# Output should show: "version": "2.0.4"
# Verify npm is installed
npm --version
# Check npm registry
npm config get registry
# Should show: https://registry.npmjs.org/# Login to npm registry
npm login
# You will be prompted for:
# - Username: th30d4y
# - Password: [your npm password]
# - Email: [your registered email]
# - OTP: [if 2FA is enabled, provide the one-time password]# From the frontend directory where package.json is located
npm publish
# Expected output:
# npm notice
# npm notice 📦 @th30d4y/openlearnx@2.0.4
# npm notice === Tarball Contents ===
# npm notice ...
# npm notice === Dist Files ===
# npm notice ...
# npm notice === Tarball Details ===
# npm notice name: @th30d4y/openlearnx
# npm notice version: 2.0.4
# npm notice filename: th30d4y-openlearnx-2.0.4.tgz
# npm notice published: [timestamp]
# npm notice public
# npm notice url: https://www.npmjs.com/package/@th30d4y/openlearnx
# npm notice access: public
# npm notice...# Check the package on NPM registry
npm view @th30d4y/openlearnx
# Check specific version
npm view @th30d4y/openlearnx@2.0.4
# You should see:
# @th30d4y/openlearnx@2.0.4 | ISC | deps: 39 | versions: 2# Test in a clean directory
mkdir /tmp/test-openlearnx && cd /tmp/test-openlearnx
npm init -y
npm install @th30d4y/openlearnx@2.0.4
# Verify the installation
npm list @th30d4y/openlearnx
# Should show: @th30d4y/openlearnx@2.0.4cd frontend
npm ci # Install exact versions from package-lock.json
npm publishSolution: Run npm login and verify your credentials
Solution:
- Verify you're logged in:
npm whoami - Check package name in package.json matches your npm account
- Ensure you have publish permissions for the package
Solution:
- Use a different version number
- Use
npm unpublish @th30d4y/openlearnx@2.0.4(if allowed) and republish
Solution: These are usually non-critical warnings. Review them but the publish should still succeed.
-
Update the GitHub Release:
- Go to https://github.com/th30d4y/OpenLearnX-ghsa-223g-f5mq-gw33/releases
- Create a new release for tag v2.0.4
- Use the RELEASE_NOTES_v2.0.4.md content
-
Announce the Release:
- Update project README with new version
- Notify users of the security update
- Recommend immediate upgrade
-
Verify in Package Managers:
- NPM: https://www.npmjs.com/package/@th30d4y/openlearnx
- Check latest version shows 2.0.4
Package Name: @th30d4y/openlearnx
Version: 2.0.4
Description: AI-powered learning platform with adaptive quizzes, coding practice, course tracking, and dashboard analytics
Repository: https://github.com/th30d4y/OpenLearnX
Registry: https://registry.npmjs.org
# Install the latest version (2.0.4)
npm install @th30d4y/openlearnx@2.0.4
# Or install the latest
npm install @th30d4y/openlearnx@latestSecurity Note: This version (2.0.4) contains critical security fixes for the JWT signature verification vulnerability (GHSA-223g-f5mq-gw33). All users should upgrade immediately.