Skip to content

Commit 9b08296

Browse files
authored
Merge branch 'main' into automation/vendor-portal-release-notes-v2025.06.23-0
2 parents b4247f9 + 50f6d52 commit 9b08296

File tree

4 files changed

+84
-15
lines changed

4 files changed

+84
-15
lines changed

docs/release-notes/rn-vendor-platform.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,13 @@ Released on June 23, 2025
1717
### Bug Fixes {#bug-fixes-v2025-06-23-0}
1818
* Show correct updated date in Customer Manage page.
1919

20+
## v2025.06.23-1
21+
22+
Released on June 23, 2025
23+
24+
### New Features {#new-features-v2025-06-23-1}
25+
* Adds Vendor API route for listing install attempts. For more information, see [enterprisePortal](https://replicated-vendor-api.readme.io/reference/listinstallattempts) in the Vendor API v3 documentation.
26+
2027
## v2025.06.18-2
2128

2229
Released on June 18, 2025

docs/vendor/enterprise-portal-about.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ The following shows an example of the Enterprise Portal dashboard:
2727

2828
* Air gap instance records do not appear in the Enterprise Portal until the vendor uploads a support bundle for that instance. For more information, see [View Active and Inactive Instances](/vendor/enterprise-portal-use#view-active-and-inactive-instances) in _Access and Use the Enterprise Portal_.
2929

30+
* Installation and upgrade instructions are available only for Embedded Cluster and Helm installations. The Enterprise Portal does not provide instructions for installing and upgrading with KOTS in existing clusters.
31+
3032
## Comparison to the Download Portal
3133

3234
The Enterprise Portal is the next generation version of the Replicated Download Portal. Compared to the Download Portal, the Enterprise Portal not only provides access to installation assets and instructions, but also allows users to track available updates, manage their team and service accounts, view the status of their instances, view license details, and more. These features are designed to make it easier for your customers to manage their instances of your application from a centralized location outside of the installation environment.
@@ -64,4 +66,4 @@ The following shows an example of the **Install Attempts** section:
6466

6567
<img alt="Install attempts section of customer reporting page" src="/images/customer-reporting-install-attempts-expanded.png" width="700px"/>
6668

67-
[View a larger version of this image](/images/customer-reporting-install-attempts-expanded.png)
69+
[View a larger version of this image](/images/customer-reporting-install-attempts-expanded.png)

package-lock.json

Lines changed: 72 additions & 12 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,12 @@
1818
"generate-llms": "node static/js/generate-llms.js"
1919
},
2020
"dependencies": {
21-
"@algolia/client-search": "^5.27.0",
21+
"@algolia/client-search": "^5.29.0",
2222
"@babel/traverse": "^7.27.4",
2323
"@docusaurus/core": "3.8.1",
2424
"@docusaurus/preset-classic": "3.8.1",
2525
"@mdx-js/react": "^3.1.0",
26-
"@types/node": "24.0.1",
26+
"@types/node": "24.0.3",
2727
"@types/react": "19.1.8",
2828
"clsx": "^2.1.1",
2929
"immer": "^10.1.1",

0 commit comments

Comments
 (0)