s.date in gemspec forces me to backdate

fookh's Avatar

fookh

15 Jan, 2019 02:06 AM

I've successfully pushed a couple gems to rubygems previously without hiccups. Starting this weekend Jan 12-Jan14, I am experiencing an odd problem.

Essentially, I am unable to set s.date in my gemspec to the current date. I have attached a couple of screencaps indicating this.

As a result my last few gems haven't popped up under "new releases - all gems" page on rubygems. So my last releases have not been downloaded at all. IDK if this is on my end or a general bug? Please advise. Thank you.

My 1st screenshot show the result when I attempt to build without backdating
My 2nd screencap shows I backdate my gemspec
My 3rd screencap again show the successful build after backdating.

  1. Support Staff 1 Posted by kerrizor on 25 Jan, 2019 04:26 PM

    kerrizor's Avatar

    Hmm, I'm not replicating this on my end. Which version of rubygems/bundler are you using? I've seen this error before when the date string was invalid.. are you manually hardcoding this value in your previous code? Since it is evaluated at the time of release, perhaps try DateTime?

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Already uploaded files

  • Screenshot_from_2019-01-14_20-49-44.png 295 KB
  • Screenshot_from_2019-01-14_20-45-01.png 200 KB
  • Screenshot_from_2019-01-14_20-51-48.png 263 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac