Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

Hello folks (and mostly spryker-staff 😉 ) Is it possible that - for example

Options
s.kroll
s.kroll Head of Technology Spryker @ basecom Posts: 117 ✨ - Novice

Hello folks (and mostly spryker-staff 😉 )
Is it possible that - for example https://github.com/spryker-feature/configurable-bundle - is missing the older release-versions and/or tags? It once definitely had a 202001.0 tag (and release) which is gone now. Could the tags/releases be re-added to restore BC?

Comments

  • Unknown
    Options

    Hi Sebastian.
    I checked our internal logs. We have a double-log of all releases and we cannot find any such tag.
    We also never remove GitHub tags (and do not allow any system to do so). As such, it seems unlikely we ever produced this package tag you mentioned.
    Do you have any additional data here that could clarify the situation?
    The feature itself got indeed created August 2019 - as internal draft. Our first log of release is though this 2020-09 milestone.

    Before that I can only assume one used the modules manually where needed.

  • Unknown
    Options

    I dug a bit deeper
    It used dev-master here thanks to aliasing.

            {
                "name": "spryker-feature/configurable-bundle",
                "version": "dev-master",
                "source": {
                    "type": "git",
                    "url": "<https://github.com/spryker-feature/configurable-bundle.git>",
                    "reference": "c0ffe79481b8c80d0d1dc165707050c3502c33bd"
                },
                "dist": {
                    "type": "zip",
                    "url": "<https://api.github.com/repos/spryker-feature/configurable-bundle/zipball/c0ffe79481b8c80d0d1dc165707050c3502c33bd>",
                    "reference": "c0ffe79481b8c80d0d1dc165707050c3502c33bd",
                    "shasum": ""
                },
                "require": {
                    "php": ">=7.2",
                    "spryker-shop/configurable-bundle-note-widget": "^1.0.0",
                    "spryker-shop/configurable-bundle-page": "^1.0.0",
                    "spryker-shop/configurable-bundle-widget": "^1.0.0",
                    "spryker-shop/sales-configurable-bundle-widget": "^1.0.0",
                    "spryker/configurable-bundle": "^2.0.0",
                    "spryker/configurable-bundle-cart": "^1.0.0",
                    "spryker/configurable-bundle-data-import": "^0.2.0",
                    "spryker/configurable-bundle-gui": "^1.0.0",
                    "spryker/configurable-bundle-note": "^1.0.0",
                    "spryker/configurable-bundle-page-search": "^1.0.0",
                    "spryker/configurable-bundle-storage": "^2.0.0",
                    "spryker/sales-configurable-bundle": "^1.0.0"
                },
                "type": "metapackage",
                "extra": {
                    "branch-alias": {
                        "dev-master": "202001.x-dev"
                    }
                },
                "notification-url": "<https://packagist.org/downloads/>",
                "license": [
                    "proprietary"
                ],
                "description": "Configurable Bundle [feature]",
                "time": "2019-12-06T10:34:30+00:00"
            },
    

    So it worked at the time thanks to branch.aliasing, and silently used master for it.
    If you use "dev-master#COMMITHASH as 202001.01"
    you can reproduce the former "pseudo tag" for now.
    We will check if we can make a backport possible here, though.

  • s.kroll
    s.kroll Head of Technology Spryker @ basecom Posts: 117 ✨ - Novice
    Options

    Interesting. We once started a project on the 202001.0 release so I read lots of ***: "^202001.0", in the composer file. for other spryker-feature-packages the tag still exists but not for spryker-feature/configurable-bundle . That is why for example other composer-updates no fail. It works when I change the require to "spryker-feature/configurable-bundle": "dev-master#c0ffe79", (which was the commit-hash to the time of the release mentioned above)

  • Unknown
    Options

    OK, any other features that are affected? Or did only this one not get the proper release at the time?

  • s.kroll
    s.kroll Head of Technology Spryker @ basecom Posts: 117 ✨ - Novice
    Options

    ok, thank you @UQK3ZPJEN 🙂

  • s.kroll
    s.kroll Head of Technology Spryker @ basecom Posts: 117 ✨ - Novice
    Options

    for now only this package blocked the updates in our project. If I find another one I let you know

  • Unknown
    Options

    I also checked the raw .lock file, and it seems there was only this one "version": "dev-master" usage.
    I was able to tag a backport release on this:
    https://github.com/spryker-feature/configurable-bundle/releases/tag/202001.0
    Please let me know if there is anything else left on this topic.