You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+20-16
Original file line number
Diff line number
Diff line change
@@ -142,27 +142,31 @@ npm list -g oad # Should denote no packages installed
142
142
## Publish the package
143
143
144
144
- Ensure you bumped the package version in [`openapi-diff`]`package.json`.
145
-
- Queue a run of the [`openapi-diff-build`] and approve the 'publish' stage.
146
-
- Verify in [`@azure/oad` versions] the package was published on npmjs.org.
145
+
- Queue a run of the [`openapi-diff` pipeline] and approve the `publish` stage. (Note: there is also the [`public.openapi-diff` pipeline] for CI checks.)
146
+
- Verify in [`@azure/oad` versions]that the newest package version was published on npmjs.org. You can also run `npm show @azure/oad`.
147
147
- Save it to `openapi-platform` feed via [upstream feeds of `openapi-platform`].
148
+
- For the desired version, you must click `Save to feed` in the context menu of the hidden triple-dot button on the right. It will reveal on hover.
149
+
- You may need to wait a bit until the newest version shows up in the `Upstream Versions` tab.
148
150
- To make `openapi-alps` use the newly published package:
149
-
- Ensure that you update the minimum package version in relevant `package.json` files and then run `rush update` and commit the changes.
150
-
- ❗ Do the update even if semver rules say the new package version is in scope. E.g. if the version is `~0.10.7` but you published `0.10.8`, then still update the entry to `~0.10.8`.
151
-
- If you will not modify any `package.json` at all, rush will not recognize the newly published package version. This can be worked around by running `rush update --full`, but this is discouraged.
152
-
- Example file: [`private/azure-swagger-validation/azureSwaggerValidation/package.json`][azureSwaggerValidation package.json]
153
-
- Example `openapi-alps` PR doing the package update: [#537791]
154
-
- Redeploy relevant `openapi-alps` parts to pick up the new package, even if you didn't had to commit any changes. Follow [this doc][openapi-alps doc].
151
+
- Ensure that you update the minimum package version in relevant [`package.json`][azureSwaggerValidation package.json] files and then run `rush update` and commit the changes.
152
+
- ❗ Do the update even if semver rules say the new package version is in scope. E.g. if the version is `~0.10.7` but you published `0.10.8`, then still update the entry to `~0.10.8`.
153
+
- If you will not modify any `package.json` at all, rush will not recognize the newly published package version. This can be worked around by running `rush update --full`, but this is discouraged.
154
+
- Example file: [`private/azure-swagger-validation/azureSwaggerValidation/package.json`][azureSwaggerValidation package.json].
155
+
- Example `openapi-alps` PR doing the package update: [#537791].
156
+
- Redeploy relevant `openapi-alps` parts to pick up the new package, even if you didn't had to commit any changes. Follow [this doc][openapi-alps doc].
0 commit comments