Release of API version 1.0.0-rc.1 (don't merge, to be closed)

[bigludo7]

What type of PR is this?

Add one of the following kinds:

• documentation
• subproject management

Note: this PR has exactly same contents than #121 that was closed because of branch issue

What this PR does / why we need it:

Generation of first release-candidate for NumberVerification API

This first release candidate r1.1 contains the definition and documentation of the release-candidate of the NumberVerification API v1.0.0-rc.1.

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.03s
✅ OPENAPI	spectral	1		0	1.61s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.72s
✅ YAML	yamllint	1		0	0.29s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[hdamker]

number_verification.yaml seems to been uploaded as a new file in 435b7bd.

GitHub is showing that all lines were replaced, which makes it difficult to see the actual changes, especially the ones from the following commits here in the PR.

[fernandopradocabrillo]

number_verification.yaml seems to been uploaded as a new file in 435b7bd.

GitHub is showing that all lines were replaced, which makes it difficult to see the actual changes, especially the ones from the following commits here in the PR.

Hi @hdamker, I'm trying to fix this but I can't commit into the PR. It seems that it's locked. As admin, do you have permissions to unlock it? Converting it to draft doesn't seem to work

[hdamker]

@fernandopradocabrillo I have no clue why this PR should have been locked, but I thought it is anyway easier to recreate the originally PR #121, but just against the correct base branch (i.e. main). Therefore I recreated the branch https://github.com/camaraproject/NumberVerification/tree/bigludo7-patch-2 and used it to open the new PR #126.
(It would have even been possible to just edit the base path in PR #121, but not after it was closed and I deleted the previous base path).

What is left do do is to redo the following commits:

83fd1a2, 65b1db0, and 73ee72f

But I would recommend to do them not in #126 but in a separate PR before the #126 get's merged and the release done.

[hdamker]

This PR shouldn't be merged but closed, it is replace by #126, but see also #123 (comment)

[hdamker]

What is left do do is to redo the following commits:

83fd1a2, 65b1db0, and 73ee72f

But I would recommend to do them not in #126 but in a separate PR before the #126 get's merged and the release done.

I've opened #127 for that.

[hdamker]

Closing it and deleting the branch