Properly Incorporating Your Updates To My Chirpy Blog #1634
-
Checklist
How did you create the site?Generated from Description
Operations you have already triedI believe the correct methodology for upgrading is: Is this all correct? Anything else?my site is bethanybeachbum.github.io |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Yes, that's all correct. I would just add that you can find the Chirpy version on the Releases tab, which contains all the release notes. Also, not every release requires you to manually update your version number. By default, every time your blog is built and deployed, it will use the latest available patch version. You have control over this process, and it depends on the dependency pattern you define. You can read more about Ruby patterns. So if your pattern is defined as |
Beta Was this translation helpful? Give feedback.
-
Is this process the same as when I created the site by cloning the repo instead of using the starter? |
Beta Was this translation helpful? Give feedback.
Yes, that's all correct.
I would just add that you can find the Chirpy version on the Releases tab, which contains all the release notes.
Also, not every release requires you to manually update your version number. By default, every time your blog is built and deployed, it will use the latest available patch version. You have control over this process, and it depends on the dependency pattern you define. You can read more about Ruby patterns. So if your pattern is defined as
~> 6.5 >= 6.5.5
, then when version6.5.6
is released, all you have to do is build and publish your blog, and it will use the latest version. However, when major version7.0
is released, you will need to follow the upg…