1.0.19 • Published 8 months ago
@teleporthq/cms-mappers v1.0.19
teleport-cms-mappers
Mapping utilities for understanding external headless CMS data.
Release process
Once the changes are merged into the main
branch.
- Always make sure, you make a
tag
from the version. - And always bump only the
patch
version. - Create a release on the GitHub repo with the same tag name.
Why we need to bump only the patch version?
Eg: 1.0.4 -> becomes 1.0.5
Since at the time of installation, the package managers pull the latest patch version available.
1.0.19
8 months ago
1.0.18
9 months ago
1.0.17
10 months ago
1.0.16
10 months ago
1.0.11
12 months ago
1.0.15
11 months ago
1.0.14
12 months ago
1.0.13
12 months ago
1.0.12
12 months ago
1.0.10
2 years ago
1.0.9
2 years ago
1.0.8
2 years ago
1.0.7
2 years ago
1.0.6
2 years ago
1.0.5
2 years ago
1.0.4
2 years ago
1.0.3
2 years ago
1.0.2
2 years ago
1.0.1
2 years ago
1.0.0
2 years ago