Skip to content

Release v1.4.0 #338

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

Merged
merged 34 commits into from
Mar 19, 2018
Merged

Release v1.4.0 #338

merged 34 commits into from
Mar 19, 2018

Conversation

sauloperez
Copy link
Collaborator

@sauloperez sauloperez commented Mar 19, 2018

These are the changes for the new release v1.4.0. Including:

Let's give a warm welcome to @Morantron! #332 is his first contribution to TimeOverflow! 👏 👏

knoopx and others added 30 commits January 26, 2018 20:00
(cherry picked from commit f41ec64)

Conflicts:
	Gemfile
	Gemfile.lock
…because of our old infra (shelly cloud). We are now running pro with Unicorn and WEBrick should be enough for dev (https://schneems.com/2017/08/01/is-webrick-webscale/). Thin is nice, but it depends on eventmachine and this a big dep we can avoid. I also update the Procfile to run Unicorn on Heroku (https://devcenter.heroku.com/articles/rails-unicorn#procfile).
… severity security vulnerability, as per GitHub security alerts, and closes #280
Includes the keys added in PR #299.
It was totally outdated regarding current DB schema. I neither found any reference on the infrastructure side (provisioning repo). So time to ✂️
…m from runtime deps since it's not used for production (nor staging) at this point. And I can't found either any reference on the wiki.
…have 1 static page, so this simple approach (1 controller) should be enough.
@sauloperez
Copy link
Collaborator Author

sauloperez commented Mar 19, 2018

Deployed on staging and working.

@sauloperez sauloperez merged commit 6f091fd into master Mar 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants