Fix version tagging on releases

Author: zkoppert

CONTRIBUTING.md

@@ -99,5 +99,7 @@ Once the code is ready to release please do the following
 5. Clone the repository at the release tag locally or in a codespace
 6. Authenticate to ghcr.io using [these instructions](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry)
 7. `docker build -t ghcr.io/zkoppert/innersource-crawler:v1 .` where v1 is the current major version number
-8. `docker push ghcr.io/zkoppert/innersource-crawler:v1` where v1 is the current major version number
-9. Update the `README.md` instructions to point to the new docker container
+8. `docker build -t ghcr.io/zkoppert/innersource-crawler:v1.0.0 .` where v1.0.0 is the full version number
+9. `docker push ghcr.io/zkoppert/innersource-crawler:v1` where v1 is the current major version number
+10. `docker push ghcr.io/zkoppert/innersource-crawler:v1.0.0` where v1.0.0 is the full version number
+11. Update the `action.yml` and `README.md` instructions to point to the new docker container if its a major version number change