fix: update environment current urls

Author: Swiftwork

packages/browser-sdk/README.md

@@ -6,7 +6,7 @@ Bucket supports feature toggling, tracking feature usage, [collecting feedback](
 
 ## Install
 
-First find your `publishableKey` under [environment settings](https://app.bucket.co/envs/current/settings/app-environments) in Bucket.
+First find your `publishableKey` under [environment settings](https://app.bucket.co/env-current/settings/app-environments) in Bucket.
 
 The package can be imported or used directly in a HTML script tag:
 

packages/browser-sdk/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bucketco/browser-sdk",
-  "version": "3.3.3",
+  "version": "3.3.4",
   "packageManager": "yarn@4.1.1",
   "license": "MIT",
   "repository": {

packages/browser-sdk/src/toolbar/Features.tsx

@@ -111,7 +111,7 @@ function FeatureRow({
         <Feature class="feature-icon" />
         <a
           class="feature-link"
-          href={`${appBaseUrl}/envs/current/features/by-key/${feature.key}`}
+          href={`${appBaseUrl}/env-current/features/by-key/${feature.key}`}
           rel="noreferrer"
           tabIndex={index + 1}
           target="_blank"

packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bucketco/cli",
-  "version": "2.0.1",
+  "version": "2.0.2",
   "packageManager": "yarn@4.1.1",
   "description": "CLI for Bucket service",
   "main": "./dist/index.js",

packages/cli/utils/urls.ts

@@ -22,7 +22,7 @@ export const baseUrlSuffix = (baseUrl: string) => {
 };
 
 export function environmentUrl(baseUrl: string, environment: UrlArgs): string {
-  return `${baseUrl}/envs/${slug(environment)}`;
+  return `${baseUrl}/env-current${slug(environment)}`;
 }
 
 export function featureUrl(

packages/node-sdk/README.md

@@ -56,7 +56,7 @@ You can also [use the HTTP API directly](https://docs.bucket.co/api/http-api)
 
 ## Basic usage
 
-To get started you need to obtain your secret key from the [environment settings](https://app.bucket.co/envs/current/settings/app-environments)
+To get started you need to obtain your secret key from the [environment settings](https://app.bucket.co/env-current/settings/app-environments)
 in Bucket.
 
 > [!CAUTION]
@@ -65,7 +65,7 @@ in Bucket.
 
 Bucket will load settings through the various environment variables automatically (see [Configuring](#configuring) below).
 
-1. Find the Bucket secret key for your development environment under [environment settings](https://app.bucket.co/envs/current/settings/app-environments) in Bucket.
+1. Find the Bucket secret key for your development environment under [environment settings](https://app.bucket.co/env-current/settings/app-environments) in Bucket.
 2. Set `BUCKET_SECRET_KEY` in your `.env` file
 3. Create a `bucket.ts` file containing the following:
 

packages/openfeature-browser-provider/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bucketco/openfeature-browser-provider",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "packageManager": "yarn@4.1.1",
   "license": "MIT",
   "repository": {
@@ -35,7 +35,7 @@
     }
   },
   "dependencies": {
-    "@bucketco/browser-sdk": "3.3.3"
+    "@bucketco/browser-sdk": "3.3.4"
   },
   "devDependencies": {
     "@bucketco/eslint-config": "0.0.2",

packages/react-sdk/README.md

@@ -171,7 +171,7 @@ generates a `check` event.
 
 The `<BucketProvider>` initializes the Bucket SDK, fetches features and starts listening for automated feedback survey events. The component can be configured using a number of props:
 
-- `publishableKey` is used to connect the provider to an _environment_ on Bucket. Find your `publishableKey` under [environment settings](https://app.bucket.co/envs/current/settings/app-environments) in Bucket,
+- `publishableKey` is used to connect the provider to an _environment_ on Bucket. Find your `publishableKey` under [environment settings](https://app.bucket.co/env-current/settings/app-environments) in Bucket,
 - `company`, `user` and `otherContext` make up the _context_ that is used to determine if a feature is enabled or not. `company` and `user` contexts are automatically transmitted to Bucket servers so the Bucket app can show you which companies have access to which features etc.
   > [!Note]
   > If you specify `company` and/or `user` they must have at least the `id` property, otherwise they will be ignored in their entirety. You should also supply anything additional you want to be able to evaluate feature targeting against,

packages/react-sdk/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bucketco/react-sdk",
-  "version": "3.3.2",
+  "version": "3.3.3",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -34,7 +34,7 @@
     }
   },
   "dependencies": {
-    "@bucketco/browser-sdk": "3.3.3",
+    "@bucketco/browser-sdk": "3.3.4",
     "canonical-json": "^0.0.4",
     "rollup": "^4.2.0"
   },

packages/vue-sdk/README.md

@@ -112,7 +112,7 @@ generates a `check` event.
 
 The `<BucketProvider>` initializes the Bucket SDK, fetches features and starts listening for automated feedback survey events. The component can be configured using a number of props:
 
-- `publishableKey` is used to connect the provider to an _environment_ on Bucket. Find your `publishableKey` under [environment settings](https://app.bucket.co/envs/current/settings/app-environments) in Bucket,
+- `publishableKey` is used to connect the provider to an _environment_ on Bucket. Find your `publishableKey` under [environment settings](https://app.bucket.co/env-current/settings/app-environments) in Bucket,
 - `company`, `user` and `otherContext` make up the _context_ that is used to determine if a feature is enabled or not. `company` and `user` contexts are automatically transmitted to Bucket servers so the Bucket app can show you which companies have access to which features etc.
 
   > [!Note]