Skip to content
This repository has been archived by the owner on Jan 9, 2025. It is now read-only.

feat: document release stages and versions #70

Conversation

jvallesm
Copy link
Collaborator

@jvallesm jvallesm commented Mar 14, 2024

Because

  • The definitions.json structure relies on dev knowledge.
  • CONTRIBUTING guidelines have outdated info

This commit

  • Corrects outdated info
  • Adds a section about how to bump the version of a component and how to keep it aligned with the release version.

@jvallesm jvallesm self-assigned this Mar 14, 2024
Copy link

codecov bot commented Mar 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.94%. Comparing base (90ea333) to head (d54e06c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #70   +/-   ##
=======================================
  Coverage   44.94%   44.94%           
=======================================
  Files           6        6           
  Lines        1117     1117           
=======================================
  Hits          502      502           
  Misses        527      527           
  Partials       88       88           
Flag Coverage Δ
unittests 44.94% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jvallesm jvallesm force-pushed the jvalles/ins-3860-document-how-to-create-a-coming-soon-open-for-contributions branch from 7f961d4 to d54e06c Compare March 14, 2024 18:15
@jvallesm jvallesm marked this pull request as ready for review March 14, 2024 18:15
@jvallesm jvallesm merged commit 91457dc into main Mar 15, 2024
8 checks passed
@jvallesm jvallesm deleted the jvalles/ins-3860-document-how-to-create-a-coming-soon-open-for-contributions branch March 15, 2024 07:39
donch1989 pushed a commit that referenced this pull request Mar 29, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.14.0-beta](v0.13.0-beta...v0.14.0-beta)
(2024-03-29)


### Features

* document release stages and versions
([#70](#70))
([91457dc](91457dc))
* merge connector and operator repos into this repo
([#72](#72))
([2fd6b1d](2fd6b1d))
* read release stage in auto generated docs from field in definitions
([#68](#68))
([90ea333](90ea333))
* remove pre-release label in version
([#75](#75))
([f0320d3](f0320d3))


### Bug Fixes

* document pre-release version removal
([#71](#71))
([e527a11](e527a11))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
namwoam pushed a commit to namwoam/component that referenced this pull request Jun 24, 2024
Because

- The `definitions.json` structure relies on dev knowledge.
- CONTRIBUTING guidelines have outdated info

This commit

- Corrects outdated info
- Adds a section about how to bump the version of a component and how to
keep it aligned with the release version.
namwoam pushed a commit to namwoam/component that referenced this pull request Jun 24, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.14.0-beta](instill-ai/component@v0.13.0-beta...v0.14.0-beta)
(2024-03-29)


### Features

* document release stages and versions
([instill-ai#70](instill-ai#70))
([91457dc](instill-ai@91457dc))
* merge connector and operator repos into this repo
([instill-ai#72](instill-ai#72))
([2fd6b1d](instill-ai@2fd6b1d))
* read release stage in auto generated docs from field in definitions
([instill-ai#68](instill-ai#68))
([90ea333](instill-ai@90ea333))
* remove pre-release label in version
([instill-ai#75](instill-ai#75))
([f0320d3](instill-ai@f0320d3))


### Bug Fixes

* document pre-release version removal
([instill-ai#71](instill-ai#71))
([e527a11](instill-ai@e527a11))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants