@tylertech/forge 3.8.1 → 3.9.0-dev.0

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 (40) hide show
  1. package/README.md +23 -0
  2. package/custom-elements.json +1263 -876
  3. package/dist/lib.js +18 -18
  4. package/dist/lib.js.map +3 -3
  5. package/dist/toolbar/forge-toolbar.css +1 -0
  6. package/dist/vscode.css-custom-data.json +37 -37
  7. package/dist/vscode.html-custom-data.json +138 -78
  8. package/esm/calendar/calendar-adapter.d.ts +24 -0
  9. package/esm/calendar/calendar-adapter.js +67 -1
  10. package/esm/calendar/calendar-constants.d.ts +34 -0
  11. package/esm/calendar/calendar-constants.js +33 -0
  12. package/esm/calendar/calendar-core.d.ts +60 -0
  13. package/esm/calendar/calendar-core.js +220 -2
  14. package/esm/calendar/calendar-dom-utils.d.ts +6 -0
  15. package/esm/calendar/calendar-dom-utils.js +36 -0
  16. package/esm/calendar/calendar.d.ts +40 -1
  17. package/esm/calendar/calendar.js +80 -2
  18. package/esm/calendar/core/calendar-base.d.ts +3 -0
  19. package/esm/calendar/core/date-range.d.ts +2 -0
  20. package/esm/calendar/core/date-range.js +1 -0
  21. package/esm/date-picker/base/base-date-picker-constants.d.ts +3 -0
  22. package/esm/date-picker/base/base-date-picker-constants.js +3 -0
  23. package/esm/date-picker/base/base-date-picker-core.d.ts +15 -0
  24. package/esm/date-picker/base/base-date-picker-core.js +30 -0
  25. package/esm/date-picker/base/base-date-picker.d.ts +12 -0
  26. package/esm/date-picker/base/base-date-picker.js +24 -0
  27. package/esm/date-picker/date-picker-core.d.ts +3 -0
  28. package/esm/date-picker/date-picker-core.js +20 -0
  29. package/esm/date-range-picker/date-range-picker-constants.d.ts +3 -0
  30. package/esm/date-range-picker/date-range-picker-constants.js +1 -0
  31. package/esm/date-range-picker/date-range-picker-core.d.ts +3 -0
  32. package/esm/date-range-picker/date-range-picker-core.js +62 -2
  33. package/esm/date-range-picker/date-range-picker.d.ts +3 -0
  34. package/esm/date-range-picker/date-range-picker.js +3 -0
  35. package/esm/split-view/split-view-panel/split-view-panel.js +1 -1
  36. package/esm/toolbar/toolbar.js +1 -1
  37. package/package.json +2 -2
  38. package/sass/calendar/_mixins.scss +3 -2
  39. package/sass/toolbar/_core.scss +5 -0
  40. package/sass/toolbar/toolbar.scss +4 -0
package/README.md CHANGED
@@ -35,6 +35,27 @@ You can also view the Storybook documentation site by running:
35
35
  npm run storybook
36
36
  ```
37
37
 
38
+ ## Release Process
39
+
40
+ This repository uses [Auto](https://intuit.github.io/auto/) for it's release process. This tool relies on conventional commits to determine the next version number
41
+ and changelog entries, as well as GitHub labels to determine the semantic version release type.
42
+
43
+ When creating a pull request, please ensure that you follow the [conventional commit guidelines](https://www.conventionalcommits.org/en/v1.0.0/) and use the appropriate labels
44
+ for the type of change you are making.
45
+
46
+ Semantic labels:
47
+
48
+ - `patch`: A bug fix that does not break any existing functionality.
49
+ - `minor`: A new feature that does not break any existing functionality.
50
+ - `major`: A breaking change that requires changes to existing code. This will bump the major version number and create a new version branch for the current major version.
51
+ - `skip-release`: Add this label when merging a PR that either does not require a release, or if you need to batch multiple changes together where only the last one merged
52
+ triggers the release.
53
+
54
+ When you are ready to release, make sure that the `skip-release` label does **not** exist on the PR, and that it contains one of the other semantic version labels noted above.
55
+ When that PR is merged, Auto will automatically create a new release and publish it to NPM. The release will be tagged with the version number, and a new [GitHub release][8] will
56
+ be created with the changelog entries for that release. Additionally, we also have a GitHub Action that pushes the bundled library code to the Forge CDN. Keep an eye on the
57
+ [GitHub Actions tab][7] to see the progress of the release, and if there are any issues with the process.
58
+
38
59
  ## Need help?
39
60
 
40
61
  Please [create](https://github.com/tyler-technologies-oss/forge/issues/new/choose) a GitHub issue with any questions and we'll be glad to help!
@@ -45,4 +66,6 @@ Please [create](https://github.com/tyler-technologies-oss/forge/issues/new/choos
45
66
  [4]: https://forge.tylerdev.io/
46
67
  [5]: https://github.com/tyler-technologies-oss/forge/blob/main/CONTRIBUTING.md
47
68
  [6]: https://github.com/tyler-technologies-oss/forge/blob/main/CHANGELOG.md
69
+ [7]: https://github.com/tyler-technologies-oss/forge/actions
70
+ [8]: https://github.com/tyler-technologies-oss/forge/releases
48
71