Bump Version to 0.17.0

Author: robertcheramy

CHANGELOG.md

@@ -4,20 +4,21 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
-## [Unreleased]
+## [0.17.0 – 2025-07-18]
 
 ### Added
 - Documentation of the configuration (@robertcheramy)
 
 ### Changed
-- Update weblibs to the latest version (@robertcheramy)
+- Update weblibs to the latest versions (@robertcheramy)
 - Depend on oxidized 0.34.0 (configuration of oxidized web as an extension) (@robertcheramy)
 - Use JSON to format the node metadata in /node/show (@robertcheramy)
 
 ### Fixed
 - Run puma directly, so that it does not rename the oxidized process. Fixes: 349 (@robertcheramy)
 - Display local time correctly and use epoch as timestamps in the URLs. Fixes: #258 and #356 (@robertcheramy)
 - Hide node vars when listed in the configuration entry hide_node_vars. Fixes: #344 (@robertcheramy)
+- /node/next/: Prefer JSON.parse over JSON.load (@robertcheramy)
 
 ## [0.16.0 - 2025-03-25]
 This release introduces the possibility for an extended configuration of

docs/development.md

@@ -85,6 +85,12 @@ forget to document your changes in CHANGELOG.md.
 
 # How to release a new version of Oxidized-web?
 
+## Version numbering
+Oxidized-web versions are numbered like major.minor.patch
+- currently, the major version is 0.
+- minor is incremented when releasing new features.
+- patch is incremented when releasing fixes only.
+
 ## Review changes
 Run `git diff 0.xx.yy..master` (where `0.xx.yy` is to be changed to the last
 release) and review all the changes that have been done. Have a specific look
@@ -100,73 +106,72 @@ bundle update
 bundle outaded
 ```
 
-Retest after updating!
+Test again after updating!
 
 ## Update the weblibs to the latest versions
 ```
 npm outdated
 ```
 
-Retest after updating!
-
-## Update rubocup .rubocop_todo.yml
-Run `bundle exec rubocop --auto-gen-config`,
-and make sure `bundle exec rake` passes after it.
-
-If you change some code => Restart the release process at the beginning ;-)
+Test again after updating!
 
 ## Make sure the file permissions are correct
 Run `bundle exec rake chmod`
 
-## Test, test test!
-Run `bundle exec rake` on the git repository to check the code against rubocop and rund the
-defined tests in `/spec`.
+## Create a release branch
+Name the release branch `release/0.xx.yy`
 
-Run Oxidized-web from git against the latest Oxidized version `bundle exec oxdized`
+Update CHANGELOG.md:
+- review it
+- add release notes
+- set the new version (replace `[Unreleased]` with `[0.xx.yy – 202Y-MM-DD]`)
+
+Change the version in `lib/oxidized/web/version.rb`
 
-Run Oxidized-web from git against the latest git of Oxidized (see above).
+Upload the branch to github, make a Pull Request for it.
 
-Do not integrate late PRs into master if they do not fix issues for the release. The must wait for the next release.
+## Test!
+Run `bundle exec rake` on the git repository to check the code against rubocop
+and run the defined tests in `/spec`.
+
+Run Oxidized-web from git against the latest Oxidized version `bundle exec oxdized`
 
 When testing the web application, open the javascript console in the browser to
 see any errors.
 
-## Version numbering
-Oxidized-web versions are nummered like major.minor.patch
-- currently, the major version is 0.
-- minor is incremented when releasing new features.
-- patch is incremented when releasing fixes only.
-
 ## Release
-1. Checkout the master branch of oxidized-web. Make sure you are up to date with origin.
-2. Change the version in lib/oxidized/web/version.rb
-3. Change CHANGELOG.md to replace [Unreleased] with [0.xx.yy – 202Y-MM-DD]
-4. Run `git diff` to check your changes
-5. Commit the changes to the local git repository with a commit message “chore(release): release version 0.xx.yy”
-6. Tag the commit with `git tag -a 0.xx.yy -m "Release 0.xx.yy"`
-7. Build the gem with ‘rake build’
-8. Install an test the gem locally:
-```
+1. Merge the Pull Request into master with the commit message
+   `chore(release): release version 0.3x.y`
+2. `git pull` master
+3. Tag the commit with `git tag -a 0.xx.yy -m "Release 0.xx.yy"`
+4. Build the gem with ‘rake build’
+5. Run `git diff` to check if there have been more changes (there shouldn't)
+6. Install an test the gem locally
+```shell
 gem install --user-install pkg/oxidized-web-0.xx.yy.gem
 ~/.local/share/gem/ruby/3.1.0/bin/oxidized
 ```
+
 ## Release in github
-1. Push the commit and the tag to github:
+Push the tag to github:
 ```
-git push
 git push origin 0.xx.yy
 ```
 
-2. Make a release from the tag in github
-- Thank the contributors
-- Only describe major changes, and refer to CHANGELOG.md
+Make a release from the tag in github.
+- Take the release notes frm CHANGELOG.md
 - List new contributors (generated automatically)
+- Keep the Full Changelog (generated automatically)
 
 ## Release in rubygems
 Push the gem with ‘rake push’
 
 You need an account at rubygems which is allowed to push oxidized
 
+## Release in docker.io
+In order to release in docker.io, oxidized be released to a new version,
+as the container is build there.
+
 ## Update CHANGELOG.md for next release
 Add
 ```
@@ -181,6 +186,3 @@ Add
 ```
 And push to github
 
-## Congratulate yourself
-Great job! Treat yourself to your favorite drink, you deserve it!
-

lib/oxidized/web/version.rb

@@ -2,6 +2,6 @@
 
 module Oxidized
   module API
-    WEB_VERSION = '0.16.0'
+    WEB_VERSION = '0.17.0'
   end
 end