Plugin updated to new version after commit on trunk

  • Resolved Joao Romao

    (@joaoromao)


    9 years, 3 months ago

    Hey guys, quick question. We’ve been developing a plugin over the last year and has been great so far, development-wise.

    However, last evening we (as usual) committed our development changes into our trunk folder. What changed was this was actually interpreted as a new plugin version and thus all new users (and those who updated) got the trunk version of our plugin.

    To worsen things up, this version was not linking to our servers, rather it was connected to 127.0.0.1 so in just a few hours we got about 2,000 users unable to use our tool.

    Anyone has an idea of what might have happened here and how we can avoid it in the future?

    Thanks in advance,
    John.

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi Joao,

    What happened was that the stable tag in trunk’s readme.txt was updated to 3.0 ([1305606]) but the plugin didn’t receive a 3.0 tag. With the tag missing, the directory has nowhere to point to but trunk, as the canonical source of truth.

    To avoid that from happening in the future, I’d recommend tagging a new release before you commit to trunk, and then commit both the trunk changes and the new tag.

    Konstantin

    Thread Starter Joao Romao

    (@joaoromao)

    Konstantin, that makes sense. I’m passing this info to the development team.

    Thanks for the answer.
    John.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Plugin updated to new version after commit on trunk’ is closed to new replies.