@@ -352,7 +352,7 @@ git push origin master
352352git push origin v1.1.0
353353
354354# 7. Monitor GitHub Actions
355- # Go to: https://github.com/encryptioner /html-to-pdf-generator/actions
355+ # Go to: https://github.com/Encryptioner /html-to-pdf-generator/actions
356356# Watch the "Publish to NPM" workflow
357357
358358# 8. Verify publication
@@ -570,16 +570,56 @@ pnpm version 1.0.2
570570git push origin v1.0.2
571571```
572572
573+ ** If you need to move a tag to a different commit:**
574+
575+ This happens when you create a tag, then make additional commits (like bug fixes) and want the tag to point to the latest commit.
576+
577+ ``` bash
578+ # Scenario: You created tag v1.0.0, then made fixes, now want to move the tag
579+
580+ # 1. Commit your fixes first
581+ git add .
582+ git commit -m " fix: your fix message"
583+ git push origin pre/release/1.0.0 # or your branch
584+
585+ # 2. Delete the old tag locally
586+ git tag -d v1.0.0
587+
588+ # 3. Delete the old tag from remote (this cancels any running workflow)
589+ git push origin --delete v1.0.0
590+
591+ # 4. Create the tag again on the current commit
592+ git tag v1.0.0
593+
594+ # 5. Force push the new tag
595+ git push origin v1.0.0
596+
597+ # Alternative: Use --force flag in one step
598+ git tag -f v1.0.0 # Force create/move tag locally
599+ git push origin v1.0.0 --force # Force push to remote
600+ ```
601+
602+ ** Important Notes:**
603+ - Always commit and push your code changes BEFORE creating/moving tags
604+ - Moving a tag will restart the publish workflow from the beginning
605+ - The package.json version must match the tag version (e.g., v1.0.0 → "version": "1.0.0")
606+
573607** If the workflow fails after pushing a tag:**
5746081 . Check the GitHub Actions logs for the error
5756092 . Fix the issue in your code
576- 3 . Delete the failed tag (see above)
577- 4 . Create a new patch version tag
578- 5 . Push the new tag
610+ 3 . Commit and push the fixes
611+ 4 . Move the tag to the new commit (see above)
612+ OR delete the tag and create a new patch version
613+
614+ ** Common workflow failures and fixes:**
615+ - ** "Dependencies lock file not found"** → Commit pnpm-lock.yaml
616+ - ** "Version mismatch"** → Update package.json version to match tag
617+ - ** "Repository URL mismatch"** → Ensure repository URL in package.json matches GitHub (case-sensitive)
618+ - ** ESLint errors** → Fix linting issues or temporarily disable linter in workflow
579619
580620## Support
581621
582622For questions or issues:
583- - GitHub Issues: https://github.com/encryptioner /html-to-pdf-generator/issues
623+ - GitHub Issues: https://github.com/Encryptioner /html-to-pdf-generator/issues
584624- NPM Package: https://www.npmjs.com/package/@encryptioner/html-to-pdf-generator
585- - GitHub Actions: https://github.com/encryptioner /html-to-pdf-generator/actions
625+ - GitHub Actions: https://github.com/Encryptioner /html-to-pdf-generator/actions
0 commit comments