docs: rewrite versioning policy

Author: cjquines

.gitlab-ci.yml

@@ -7,6 +7,7 @@ image: node:20-alpine
     - apk add --no-cache git
     - git clone https://github.com/stainless-api/upload-openapi-spec-action.git
     - cd upload-openapi-spec-action
+    - npm install
     - node dist/index.js
   variables:
     INPUT_STAINLESS_API_KEY: $STAINLESS_API_KEY

README.md

@@ -124,6 +124,12 @@ beforehand. That action needs the `contents: read` permission.
 
 ### Versioning policy
 
-This action is in public beta, and breaking changes may be introduced in any
-commit. We recommend pinning your actions to a full-length commit SHA to avoid
-potential breaking changes.
+This action uses [semantic versioning](https://semver.org/), and you can pin
+your action to a major (`v1`), minor (`v1.0`), or patch (`v1.0.0`) version.
+The public API is specified by the inputs and outputs of each action. The
+following are not considered to be part of the public API:
+
+- The exact format of pull request comments, which can change between versions.
+
+- The exact format of the `outcomes` and `base_outcomes` outputs, which can
+change even within the same version.