Skip to content

Releases and tags using semantic versioning #2577

Open
@miralgj

Description

@miralgj

It would be beneficial if the project made "dot" releases or tags as bugs are fixed. This helps those of us who are deploying and upgrading specific major versions in automated or containerized environments.

Take the below snippet from a Dockerfile for example:

FROM debian:11-slim AS base

ARG VERSION=2.19

ENV WEBWORK_URL="https://github.com/openwebwork/webwork2/archive/refs/tags/WeBWorK-${VERSION}.tar.gz" \
    PG_URL="https://github.com/openwebwork/pg/archive/refs/tags/PG-${VERSION}.tar.gz"

RUN mkdir /opt/webwork

WORKDIR /opt/webwork

RUN APT_BASE_PKGS="apt-utils ca-certificates curl debconf-utils lsb-release" && \
    apt-get update && \
    apt-get install -y --no-install-recommends --no-install-suggests $APT_BASE_PKGS && \
    curl -fsSL https://deb.nodesource.com/setup_16.x | bash - && \
    apt-get install -y --no-install-recommends --no-install-suggests nodejs

RUN curl -o webwork.tar.gz -fsSLO $WEBWORK_URL && \
    curl -o pg.tar.gz -fsSLO $PG_URL && \
    mkdir webwork2 pg courses libraries && \
    tar -xzvf webwork.tar.gz -C webwork2 --strip=1 && \
    tar -xzvf pg.tar.gz -C pg --strip=1 && \
    rm -f webwork.tar.gz pg.tar.gz && \
    cd /opt/webwork/webwork2/htdocs && \
    npm ci && \
    cd /opt/webwork/pg/htdocs && \
    npm ci

...

There have been some bugfixes merged into the main branch but, because there hasn't been a new tag, a new strategy has to be adopted in the Dockerfile to pull them in (e.g. curl -o webwork.zip -fsSLO https://github.com/openwebwork/webwork2/archive/${COMMIT_SHA}.zip).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions