Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create release v0.1.0 alpha.1 #16

Closed
wants to merge 5 commits into from

Conversation

caubut-charter
Copy link
Contributor

@caubut-charter caubut-charter commented Jul 26, 2024

Create release v0.1.0-alpha.1.

What type of PR is this?

Add one of the following kinds:

  • subproject management

What this PR does / why we need it:

Prepares for an initial alpha release.

Which issue(s) this PR fixes:

N/A

Special notes for reviewers:

Changelog input

N/A

Additional documentation

Copy link

github-actions bot commented Jul 26, 2024

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.02s
✅ OPENAPI spectral 1 0 2.98s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY secretlint yes no 0.75s
✅ YAML yamllint 1 0 0.68s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

@caubut-charter
Copy link
Contributor Author

Dropping alpha also.


| Nr | API release assets | alpha | release-candidate | initial<br>public | stable<br> public | Status | Comments |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
| 1 | API definition | M | M | Y | M | Y | [link](../../code/API_definitions/network_access_management.yaml) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| 1 | API definition | M | M | Y | M | Y | [link](../../code/API_definitions/network_access_management.yaml) |
| 1 | API definition | M | M | M | M | Y | [link](../../code/API_definitions/network_access_management.yaml) |

This shouldn't have changed from the template.

@@ -132,7 +132,7 @@ info:
may be used. If an end-user replaces the equipment, all existing isolated networks SHOULD be synced to the new
device representing this mesh. Alternatively, a synthetic hardware address may also be used if the specification
for the address type allows.
version: wip
version: 0.1.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd stick with wip for now, until all of the commonalities and ICM stuff is finalized and we've incorporated it.

@caubut-charter caubut-charter deleted the chore/create-release-v0.1.0-alpha.1 branch July 26, 2024 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants