@contentful/app-sdk 4.23.0-alpha.1 → 5.0.0-alpha.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (11) hide show
  1. package/README.md +5 -8
  2. package/dist/cf-extension-api.bundled.js +1 -1
  3. package/dist/cf-extension-api.js +1 -1
  4. package/dist/types/api.types.d.ts +2 -26
  5. package/dist/types/cmaClient.types.d.ts +0 -1
  6. package/dist/types/dialogs.types.d.ts +1 -5
  7. package/dist/types/index.d.ts +2 -3
  8. package/dist/types/navigator.types.d.ts +1 -9
  9. package/package.json +1 -1
  10. package/dist/space.d.ts +0 -3
  11. package/dist/types/space.types.d.ts +0 -272
package/README.md CHANGED
@@ -33,10 +33,7 @@ A new package version is automatically published to npm using [semantic-release]
33
33
 
34
34
  To manually publish the package, run `npm run publish-all`.
35
35
 
36
- This repository is published as two packages with identical data. We recommend using `@contentful/app-sdk`.
37
-
38
- - `@contentful/app-sdk`
39
- - `contentful-ui-extensions-sdk`
36
+ This repository is published as `@contentful/app-sdk` package.
40
37
 
41
38
  #### Canary releases
42
39
 
@@ -46,11 +43,11 @@ The default and stable releases are always published under the `latest` tag (as
46
43
  The release under the `canary` tag is to be considered unstable and potentially breaking.
47
44
  You should not rely on it in production.
48
45
 
49
- To release alpha version of package follow these steps:
46
+ To start a new alpha version of the package follow these steps:
50
47
 
51
- 1. Delete the `canary` branch.
52
- 2. Create a new `canary` branch from `master`.
53
- 3. Create a new branch with your changes from `canary`.
48
+ 1. Checkout the `canary` branch.
49
+ 2. Reset canary to the latest master: `git reset --hard origin/master`
50
+ 3. Create a new branch with your changes from `canary`
54
51
  4. Create a PR that merges into `canary`.
55
52
 
56
53
  ### File Structure