https://github.com/link-foundation/lino-objects-codec/actions/runs/25279435356
We should have language specific readme for each language, with badges for latest package versions in each one. Also the main README.md file should contain badges of packages of all versions with direct links to package registries. We should have clear GitHub releases separate for each language, with release specific badges in description, title and tags should be prefixed like we do with our templates.
We also need to check for false positives, because 0.3.3 version was not published to npm. Also we didn't got split GitHub releases for each language separately. For example there is no GitHub release for Rust version of package. In python failing CI/CD it is not clear what user should do in the case of such error. So I expect the all CI/CD if fail to publish the package provide with error instructions on how to fix that.
Please focus on CI/CD, code and tests should not be changed in this pull request.
Also I want to see clear fails of
Double check if credentials are not set or expired, we clearly show that in error messages and clearly fail CI/CD. I will handle that manually later.
Use all the best practices from CI/CD templates (check full file tree to compare for all GitHub workflow and CI/CD scripts file), if the same issue is found in template report issue also in templates:
We should compare all files, so we don't have more CI/CD errors in the future and reuse all the best practices from these templates.
We need to download all logs and data related about the issue to this repository, make sure we compile that data to ./docs/case-studies/issue-{id} folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).
If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code.
Please plan and execute everything in a single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.
https://github.com/link-foundation/lino-objects-codec/actions/runs/25279435356
We should have language specific readme for each language, with badges for latest package versions in each one. Also the main README.md file should contain badges of packages of all versions with direct links to package registries. We should have clear GitHub releases separate for each language, with release specific badges in description, title and tags should be prefixed like we do with our templates.
We also need to check for false positives, because 0.3.3 version was not published to npm. Also we didn't got split GitHub releases for each language separately. For example there is no GitHub release for Rust version of package. In python failing CI/CD it is not clear what user should do in the case of such error. So I expect the all CI/CD if fail to publish the package provide with error instructions on how to fix that.
Please focus on CI/CD, code and tests should not be changed in this pull request.
Also I want to see clear fails of
Double check if credentials are not set or expired, we clearly show that in error messages and clearly fail CI/CD. I will handle that manually later.
Use all the best practices from CI/CD templates (check full file tree to compare for all GitHub workflow and CI/CD scripts file), if the same issue is found in template report issue also in templates:
We should compare all files, so we don't have more CI/CD errors in the future and reuse all the best practices from these templates.
We need to download all logs and data related about the issue to this repository, make sure we compile that data to
./docs/case-studies/issue-{id}folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code.
Please plan and execute everything in a single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.