v0.0.3-azure-pipeline

https://github.com/armornetworkdev/armor/releases/tag/v0.03-azure-pipeline
have a latest commit: 2a75c9c6e3079e2bbe1e489da714a90ba7251f60

• and then commit ce373e87f872ad27fea62cdd8a7332e0cc766814

• and then commit e569f1719e9a790241c4c0328381565df6935a21.

• and then commit 2687df04ee4620df9dc2ad3d2b475b335098e0f9

So, for this branch, and for release v0.03-azure-pipeline, the latest commit , is 2687df04ee4620df9dc2ad3d2b475b335098e0f9.

This is the same code, as here: https://github.com/armornetworkdev/armor/tree/ce373e87f872ad27fea62cdd8a7332e0cc766814

Synchronize changes with "armornetworkdev" and add binaries from releases.

Backup binaries from here v0.02-azure-pipeline
Source code of v.0.02-azure-pipeline was been merged into master-branch.
Then, new branch armor_v0.0.2-azure-pipeline was been created from that master-branch.
Now this is the same as https://github.com/armornetworkdev/armor/tree/v0.02-azure-pipeline.

This https://github.com/username1565/armor/tree/v0.0.2-azure-pipeline
is the same as this https://github.com/armornetworkdev/armor/tree/v0.02-azure-pipeline
armor_v0.0.2-azure-pipeline...armornetworkdev:v0.02-azure-pipeline
But latest commit is different, after merge changes.

Binaries downloaded from v0.02-azure-pipeline, and uploaded here.

Stable Armor v0.0.2 (backuped source code)

Stable Armor v0.0.2 (backuped source code) from https://github.com/armornetworkdev/armor

This is the same as this Release

This code is thie same as username1565/armor_v0.0.2 :
armor_v0.0.2.1-ad567c3fe167e32576b92a43c0410fa241209862...username1565:armor_v0.0.2

And this is the same as Armor-Nework/armor-ad567c3fe167e32576b92a43c0410fa241209862 :
Armor-Network/armor@armor-ad567c3fe167e32576b92a43c0410fa241209862...username1565:armor_v0.0.2

But this was bee created, after uploading files to synchronize changes.

This code is equals of code on this branch: https://github.com/armornetworkdev/armor/tree/ad567c3fe167e32576b92a43c0410fa241209862

This is (armornetworkdev/armor/v0.02)[https://github.com/armornetworkdev/armor/releases/tag/v0.02]
but with fixed link on lmdb-repositary, in workflow

Such as this is v0.02, + just one line fixed
(line 31, armor/.github/workflows/cmake.yml, noritte/lmdb.git -> armornetworkdev/lmdb.git)

So, binaries from v0.02 is attached here.

armor_v0.0.2-lmdb-fix

Backup this source code, in zip-file, in this release.

This is old Armor-Network/armor. Current Armor-Network/armor, was been forked from armornetworkdev/armor,
and next changes was been synchronized, after commit ad567c3fe167e32576b92a43c0410fa241209862.
This is backup of the code up to this commit: ad567c3fe167e32576b92a43c0410fa241209862.

This is equals of armor_v0.0.2, in this branch

v1.0.0 was been renamed to v0.0.1. The same commit there.

v1.0.0 was been renamed to v0.0.1. The same commit there.

Armor v0.0.1 (backuped source code)

Armor v0.0.1 (backuped source code, armor_v0.0.1-branch, and old master-branch, before opening this Merge Pull-Request: #2 )

This code have no binaries, but this code can be downloaded as zip-archive, and binaries can be compiled, from this source code.