Releases: engineyard/core-client-rb
v3.6.6
v3.4.5
v3.6.5
What's Changed
In this change, we have updated internal dependency to a newer version to meet changes in the EngineYard Cloud backend configuration, added some notes how to build the ey-core
gem and updated the version to 3.6.5 as well.
Here are the specific changes for this release:
- Setup development.md documentation for gem bundling by @Kyle-Law in #132
- GHI-4789 - Build the
cookiejar
gem from sources by @eudalov in #135
Full Changelog: v3.6.4...v3.6.5
About the ey-core
update
In this release, we have updated ey-core
gem re its dependency from the cookiejar
gem (we are bulding it from the sources as per the reason described in PR #135).
When a customer installs or updates the ey-core
till the latest version it should verify that the cookiejar
gem is of the latest version as well.
In our case it means that cookiejar
should be built from its GitHub sources https://github.com/dwaite/cookiejar. This can be achieved using the following commands
gem install specific_install
gem specific_install -l 'https://github.com/dwaite/cookiejar' -b master
So, to summarize the above, the customer should
- install/update
cookiejar
using 2 commands mentioned above (aboutspecific_install
) - then install
ey-core
as usual and make sure that it's of the version 3.6.5 (ey-core version
)
ey-core v3.6.4 (2021-02-02)
This version is of ey-core is to update the version to v3.6.4 and to change to a newer the faraday from 1.0.1
Here are the specific changes for this release:
#130 [FBZ-10202] Bump version and unlock faraday version
ey-core v3.6.3 (2021-10-28)
This version is of ey-core is to update the version to v3.6.3 and include v3.6.2 changes which can be found here. This change is because of v3.6.2 being yanked from RubyGems.org.
For changes please check v3.6.2 which has been referenced
References
Here are the specific changes for this release:
- #129 [FBZ-9098] Update ey-core version because of yanked gem
ey-core v3.6.2 (2021-10-27)
The focus of this release is on general improvements especially focusing around people's deployment processes with newer versions of ruby.
Changed Items
- You can now state the version of ServerSide version used in a deploy
- You can use ey-core to SSH into application master
References
Here are the specific changes for this release:
ey-core v3.6.1 (2020-06-11)
The focus of this release, aside from bug fixes and general improvement, is the beginning of an ongoing process to improve the documentation around the ey-core gem. In particular to that goal, we've updated the README that is displayed on the main GitHub page for the repo with more information about the CLI component of the gem.
Bug Fixes
- It was discovered that the
--no-migrate
flag for theey-core deploy
command was not being properly honored. This has been rectified. - It was discovered that the request object that retrieves Deployments from the API used a malformed set of options. This has been rectified.
Noteworthy Items
There are three important notes to go along with the above:
- The gem can now be used with ruby-2.7
- The gem now requires that you have at least ruby-2.5
- To make development a bit easier going foward, we've adopted the git flow branching model and have changed the default branch to
develop
.
References
Here are the specific changes for this release:
- #106 Implement Core API for retrieving docker authorization [EYPP-3071]
- #107 EYPP-3103 add discover container service deployment request [EYPP-3103]
- #108 Fix query value in get_deployments
- #112 NEW: adds name to server listing output
- #114 Fixes no migrate [TEY-328]
- #120 Upgrade dependencies [TEY-267]
- #121 Adding a bit of CLI documentation [TEY-188]