# Include the Defold version in the project files **URL:** \ **Category:** Feature requests (USE GITHUB)\ **Created:** [May 23, 2020, 6:37pm UTC](https://forum.defold.com/t/include-the-defold-version-in-the-project-files/65303 "2020-05-23T18:37:00Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![connor.halford](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/connor.halford/32/9210_2.png) [@connor.halford](https://forum.defold.com/u/connor.halford)\ **Post date:** [May 23, 2020, 6:37pm UTC](https://forum.defold.com/t/include-the-defold-version-in-the-project-files/65303/1 "2020-05-23T18:37:01Z")
It’d be great to have an indication within the files of a Defold project what version of the engine/editor it was last opened with. This is useful for a number of reasons: - When updating an old project to a new version of Defold, you will know which release notes to read to see what has changed and should therefore be updated in the project. - Very few previous versions of the editor are [available to download](https://d.defold.com/stable/) (separate request: have all older versions available, perhaps at [https://d.defold.com/archive/](https://d.defold.com/archive/) rather than /stable to make it clear they aren’t supported) - By default a project will be using many of the assets in the built-ins section, but these can and [do change](https://forum.defold.com/t/defold-1-2-147-has-been-released/43851) between versions so it’s important to be aware of what has changed (for this reason I’ve now copied the built-ins I was using, so that I have a fixed version in the project) Within the ProjectSettings folder of a Unity project is a ProjectVersion.txt file, for example: ``` m_EditorVersion: 2019.3.1f1 m_EditorVersionWithRevision: 2019.3.1f1 (89d6087839c2) ``` This is extremely helpful when upgrading a project, or for knowing which version of the editor to install if you don’t want to or can’t upgrade. This could just be added inside the game.project file at the root of each Defold project. Since Defold updates are very frequent it may be more beneficial to have it as a separate file similar to Unity to avoid unnecessary source control noise on the game.project file. ---
**Author:** ![britzl](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/britzl/32/23_2.png) [@britzl](https://forum.defold.com/u/britzl)\ **Post date:** [May 24, 2020, 6:24am UTC](https://forum.defold.com/t/include-the-defold-version-in-the-project-files/65303/2 "2020-05-24T06:24:32Z")
Connor, thank you for the feature request. Could I ask that you create this on GitHub as well and link to it here? ---
**Author:** ![Pkeod](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/pkeod/32/606_2.png) [@Pkeod](https://forum.defold.com/u/Pkeod)\ **Post date:** [May 24, 2020, 7:03am UTC](https://forum.defold.com/t/include-the-defold-version-in-the-project-files/65303/3 "2020-05-24T07:03:49Z")
This could be done with editor scripts as well though it would require one of the triggers to run the generation it should be reasonably reliable. ---
**Author:** ![connor.halford](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/connor.halford/32/9210_2.png) [@connor.halford](https://forum.defold.com/u/connor.halford)\ **Post date:** [May 25, 2020, 8:43pm UTC](https://forum.defold.com/t/include-the-defold-version-in-the-project-files/65303/4 "2020-05-25T20:43:39Z")
Sure, here you go: [https://github.com/defold/defold/issues/4843](https://github.com/defold/defold/issues/4843) Is it preferable to request features through GitHub then, rather than on the forum? ---
**Author:** ![connor.halford](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/connor.halford/32/9210_2.png) [@connor.halford](https://forum.defold.com/u/connor.halford)\ **Post date:** [May 25, 2020, 8:48pm UTC](https://forum.defold.com/t/include-the-defold-version-in-the-project-files/65303/5 "2020-05-25T20:48:20Z")
Re: making older versions of the engine/editor available for download, I’ve realised that they _are_ available through the [GitHub releases page](https://github.com/defold/defold/releases), just not from the [Defold download page](https://d.defold.com/stable/). So I guess this is already solved, although linking to the GitHub releases page for older versions from the download page would be helpful. ---
**Author:** ![britzl](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/britzl/32/23_2.png) [@britzl](https://forum.defold.com/u/britzl)\ **Post date:** [May 25, 2020, 10:06pm UTC](https://forum.defold.com/t/include-the-defold-version-in-the-project-files/65303/6 "2020-05-25T22:06:45Z")
> [@connor.halford](#): > > Is it preferable to request features through GitHub then, rather than on the forum? Not sure yet. The forum is a good place to discuss feature requests, but at some point the discussion should be moved to GitHub before any actual work starts. > [@connor.halford](#): > > Re: making older versions of the engine/editor available for download, I’ve realised that they _are_ available through the [GitHub releases page](https://github.com/defold/defold/releases), just not from the [Defold download page](https://d.defold.com/stable/). The Defold Download page ([d.defold.com](http://d.defold.com)) will keep the last 180 days of releases (stable, beta and dev builds). GitHub Releases will show all stables releases from now until someone at GitHub complains that we are using too much disk space 🙂