3 Commits

Include renames

Author	SHA1	Message	Date
ci-bot	3749f6b9ad	chore(example_bin): release v0.1.1 ... Signed-off-by: ci-bot <bot@email.melfely.com>	2026-09-11 11:20:33 -05:00
melfely	61b4892417	Merge pull request 'chore(example_lib): release v0.1.1' (#4) from release-plz-2026-09-11T01-35-29Z into melfely/release-plz ... Reviewed-on: #4 feat: bin example now references the local example_lib ci: Changed from direct secret sub to env variables	2026-09-11 11:20:33 -05:00
melfely	32d1e2cd29	ci: Added lint.yml which tests for linting and build on multiple platforms ... This uses a 3 step process Lint -> Linux x86 Build -> [Linux x86 Test, Windows x86 Build, MacOS Check, Linux aarch64 Build] The build steps being seperate from the linux build is so that its clear WHICH OS is preventing the build, along with if it doesn't build for linux x86 (MY dev machines) then there is ZERO point in checking other OS since all of my work happens on linux x86. This reduces Runtime on just outright bad pull-requests. Then we have plenty of runners, so we can easily run all 4 of the other jobs in the final step in parallel. The MacOS steps includes a build BUT will pass regardless of its output, because the build step for MacOS is fairly unrelaible, so this relies on a check only. The main difference between a check and a builds is that build calls the linker, while the check does not. Since the linker commonly fails in a cross-compile, while check verifies the rust code itself is techincally compatible with the OS. (IE no dependencies outright do not support the target). Which is a good enough for the most part.	2026-09-10 14:27:13 -05:00