nextcloud / nextcloud/cookbook

Being prompted with a v0.10.5 update however its not in the changelog

Open
#2,002 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
HTML
Stars
641
Forks
113
Avg merge
21h 31m
Merged PRs (30d)
26

Description

Description
Hi there,

I was about to update the Cookbook app on my NC to a reported v0.10.5 and went to check the changelog but it doesn't seem that such a version exists in CHANGELOG.md. It also seems that the last version bump in Github Actions was from 0.10.3 to 0.11.0-rc1.

I'm not familiar with the deployment/update workflow for NC apps but thought it worth mentioning. In the best case it's just been a manual push and there's no clear notes. Potentially it's actually updating to v0.10.3 and incorrectly reporting the version number. Worst case the h4x0r5 are coming for our cheesecakes via a malicious Cookbook update!!! 😆

Reproduction
Steps to reproduce the behavior:

  1. Install v0.10.2 of Cookbook
  2. Go to see available App updates
  3. Prompted to update to v0.10.5

Expected behavior
Only known versions of the Application should be presented.
Changelog should have detail on any deployed version.
Presumably the Github Actions (haven't looked) trigger a deployment based on the contents of last_release

Versions
Nextcloud server version: 27.1.3.2
Cookbook version: 0.10.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing CHANGELOG.md with the reported v0.10.5 update and inspect the GitHub Actions version bump from 0.10.3 to 0.11.0-rc1. Check how last_release is used in the deployment workflow and determine whether the advertised version matches a released build and its changelog entry.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.