Badges for "dev" package are not reporting the correct version

[leogr]

Describe the bug

As per the title.

How to reproduce it

Look at the README.md 👇

Expected behaviour

Badges should report the latest version on the master branch according to the following format:
x.y.z-N+hash

Where:

• x.y.z the latest released version
• N is the number of commit since the latest released version
• hash is the ID of the latest commit on the master (first 7 digits)

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

[jasondellaluce]

Hey @leogr, has this been fixed? I see the badges render as expected right now.

[leogr]

Hey @jasondellaluce

IIRC, it's partially fixed. It might not work under some circumstances. Basically, we pick the last version by relying on the S3 bucket ordering which may not reflect the version order.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

I confirm a similar issue is still present. Basically, it seems to me filenames are ordered lexicographically.
So falco-0.30.0-19+f7893fb-x86_64.deb will come after than falco-0.30.0-177+f86423d-x86_64.deb that's not ok for our use case (you can check out the full order list here).

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[poiana]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

[leogr]

/remove-lifecycle rotten

cc @FedeDP

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[FedeDP]

/remove-lifecycle stale

[leogr]

In the end, the best option was to remove them from the README.
We will work on a better way to document how to use dev packages.
/milestone 0.36.0

/close

[poiana]

@leogr: Closing this issue.

In response to this:

In the end, the best option was to remove them from the README.
We will work on a better way to document how to use dev packages.
/milestone 0.36.0

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.