Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Release Bell
  3. [GitHub API] Update your access token to the new format

[GitHub API] Update your access token to the new format

Scheduled Pinned Locked Moved Solved Release Bell
3 Posts 2 Posters 660 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • imc67I Offline
      imc67I Offline
      imc67
      translator
      wrote on last edited by
      #1

      GitHub sent me the following email, is it something I can change in ReleaseBell or is an update needed?

      We noticed that, at April 5th, 2021 at 23:25 (UTC) your authentication token (ReleaseBell, with a user-agent header of releasebell@cloudron octokit-rest.js/18.2.0 octokit-core.js/3.2.5 Node.js/14.15.4 (linux; x64)) accessed the GitHub API, the token you used has an outdated format.
      
      In order to provide additional security benefits to all our customers, we recently updated the format of our API authentication tokens. Please update your authentication tokens to take advantage of these benefits, by visiting https://github.com/settings/tokens.
      
      1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        I don't think the app needs to be updated, but only the access token needs refreshing. Once a new access token is generated on GitHub it can be set in the profile view of releasebell.

        imc67I 1 Reply Last reply
        1
        • nebulonN nebulon

          I don't think the app needs to be updated, but only the access token needs refreshing. Once a new access token is generated on GitHub it can be set in the profile view of releasebell.

          imc67I Offline
          imc67I Offline
          imc67
          translator
          wrote on last edited by
          #3

          @nebulon I added a new toke and it seems to work, thanks!

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search