-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update releaser to regenerate generated field on index update #99
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you squash the commit as well?
thanks for the fix
Currently, the only time the `generated` field is ever written is when we invoke the repo.NewIndexFile() field. This means that contrary to what you would expect, the `generated` field is not updated when the index is updated. This adds a single line change that calls `time.Now()` after we have determined that the index is to be updated, and updates the `generated` field before the index is written. Signed-off-by: Nikolas Skoufis <nskoufis@seek.com.au>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
thanks!
Bump @unguiculus |
Any chance the maintainers here can do a release, are we waiting on something else before that happens? |
@onedr0p I will check that next week |
Awesome and I just noticed someone created an issue for this, apologies for asking here. |
Currently, the only time the
generated
field is ever written is when we invoke therepo.NewIndexFile()
method. This means that contrary to what you would expect, thegenerated
field is not updated when the index is updated.This adds a single line change that calls
time.Now()
after we have determined that the index is to be updated, and updates thegenerated
field before the index is written.Closes #90