feat: create postcss-spring-easing plugin

.gitmessagetpl

@@ -0,0 +1,43 @@
+# Full spec: https://www.conventionalcommits.org/en/v1.0.0
+#
+# TYPE
+# ======================================================================
+# Can be one of: feat, fix, chore, build, ci, docs, tests, etc...
+#
+#  - a commit of the type fix patches a bug in your codebase,
+#    this correlates with PATCH in Semantic Versioning.
+#
+#  - a commit of the type feat introduces a new feature to the codebase,
+#    this correlates with MINOR in Semantic Versioning.
+#
+#  - types other than fix and feat are allowed, additional types are
+#    not mandated by the Conventional Commits specification, and have
+#    no implicit effect in Semantic Versioning
+#
+# SCOPE
+# ======================================================================
+# A scope MUST consist of a noun describing a section of the codebase
+# surrounded by parenthesis, e.g., fix(parser):
+#
+# FOOTERS
+# ======================================================================
+# Footers must also be separated by a blank line
+# from the body & be on consecutive lines.
+#
+# A commit that has a footer BREAKING CHANGE:, or appends a ! after the
+# type/scope, introduces a breaking API change (correlating with MAJOR
+# in Semantic Versioning).
+#
+# A BREAKING CHANGE can be part of commits of any type.
+#
+# Footers other than BREAKING CHANGE may be provided and follow a
+# convention similar to the git trailer format.
+# see: https://git-scm.com/docs/git-interpret-trailers
+#
+# LINE LENGTH
+# ======================================================================
+# |<----- preferably using up to 50 chars ------>|<- no more than 72 ->|
+<type>[(optional scope)][!]: <description>
+[optional body]
+
+[optional footer(s)]

.releaserc.yml

@@ -0,0 +1,53 @@
+# spec: https://semantic-release.gitbook.io/semantic-release/usage/configuration
+
+branches: ['main']
+plugins:
+  # Determine the type of release by analyzing commits.
+  # ie: Major, Minor or Patch
+  - - "@semantic-release/commit-analyzer"
+    - preset: conventionalcommits
+      releaseRules:
+        - { breaking: true, release: major }
+        - { revert: true, release: patch }
+        - { type: feat, release: minor }
+        - { type: fix, release: patch }
+        - { type: perf, release: patch }
+        - { type: docs, release: patch }
+        - { type: refactor, release: patch }
+        - { type: style, release: patch }
+        - { type: build, release: patch }
+        - { type: ci, release: patch }
+        - { type: test, release: patch }
+        - { type: update, release: patch }
+
+  # Generate CHANGELOG.md
+  - - "@semantic-release/release-notes-generator"
+    - preset: conventionalcommits
+      presetConfig:
+        # spec: https://github.com/conventional-changelog/conventional-changelog-config-spec/tree/master/versions/2.1.0
+        types:
+          - { type: feat, section: "Features" }
+          - { type: fix, section: "Bug Fixes" }
+          - { type: chore, section: "Misc" }
+          - { type: docs, section: "Misc" }
+          - { type: style, section: "Improvements" }
+          - { type: refactor, section: "Improvements" }
+          - { type: perf, section: "Improvements" }
+          - { type: test, section: "Automation" }
+          - { type: ci, section: "Automation" }
+          - { type: build, section: "Automation" }
+          - { type: update, section: "Automation" }
+
+  - "@semantic-release/changelog"
+
+  # Commit CHANGELOG.md back to repo
+  - - "@semantic-release/git"
+    - assets: ["CHANGELOG.md"]
+      message: "chore(release): update changelog ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+
+  # Create new github release
+  - - "@semantic-release/github"
+    - assets: ["lib/**"]
+
+  # Create new npm release
+  - - "@semantic-release/npm"